Electrical control system

ABSTRACT

An electrical control system.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is related to the following: U.S. utility patentapplication Ser. No. ______, attorney docket no. 23667.22, filed on Jan.13, 2006, U.S. utility patent application Ser. No. ______, attorneydocket no. 23667.99, filed on Jan. 13, 2006, U.S. utility patentapplication Ser. No. ______, attorney docket no. 23667.100, filed onJan. 13, 2006, U.S. utility patent application Ser. No. ______, attorneydocket no. 23667.101, filed on Jan. 13, 2006, U.S. utility patentapplication Ser. No. ______, attorney docket no. 23667.102, filed onJan. 13, 2006, U.S. utility patent application Ser. No. ______, attorneydocket no. 23667.291, filed on Jan. 13, 2006, and U.S. utility patentapplication Ser. No. ______, attorney docket no. 23667.292, filed onJan. 13, 2006, the disclosures of which are incorporated herein byreference.

BACKGROUND

The present disclosure relates in general to lighting and in particularto an electrical control system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of an exemplary embodiment of acontrol system.

FIG. 2 is a schematic illustration of an exemplary embodiment of masternodes.

FIG. 3 is a schematic illustration of an exemplary embodiment of slavenodes.

FIG. 4 is a schematic illustration of an exemplary embodiment of a handheld radio frequency controller.

FIG. 5 is a schematic illustration of an exemplary embodiment of thecontroller of the radio frequency controller of FIG. 4.

FIG. 6 is a schematic illustration of an exemplary embodiment of themenu state machine of the application programs of the controller of FIG.5.

FIG. 7 is a schematic illustration of an exemplary embodiment of acommunication pathway of the associate engine of the menu state machineof FIG. 6.

FIG. 8 is a schematic illustration of an exemplary embodiment of thescenes engine of the menu state machine of FIG. 6.

FIG. 9 is a schematic illustration of an exemplary embodiment of a scenein the scenes engine of FIG. 8.

FIG. 10 is a schematic illustration of an exemplary embodiment of theevent engine of the menu state engine of FIG. 6.

FIG. 11 is a schematic illustration of an exemplary embodiment of anevent in the event engine of FIG. 10.

FIG. 12 is a schematic illustration of an exemplary embodiment of thesystem panic engine of the menu state engine of FIG. 6.

FIG. 13 is a schematic illustration of an exemplary embodiment of apanic group in the system panic engine of FIG. 12.

FIG. 14 is a schematic illustration of an exemplary embodiment of theaway engine of the menu state engine of FIG. 6.

FIG. 15 is a schematic illustration of an exemplary embodiment of anaway group in the away engine of FIG. 14.

FIG. 16 is a schematic illustration of an exemplary embodiment of thememory of the radio frequency controller of FIG. 4.

FIG. 17 is a schematic illustration of an exemplary embodiment of thedevices database of the memory of FIG. 16.

FIG. 18 is a schematic illustration of an exemplary embodiment of thenode information frame for the devices database of FIG. 17.

FIG. 19 is a schematic illustration of an exemplary embodiment of thekeypad of the radio frequency controller of FIG. 4.

FIGS. 19 a and 19 b are side and front view illustrations of anexemplary embodiment of the housing of the hand held radio frequencycontroller.

FIG. 20 is a schematic illustration of an exemplary embodiment of themain menu during operation of the radio frequency controller of FIG. 4.

FIG. 21 is a flow chart illustration of an exemplary embodiment of amethod of operating the radio frequency controller of FIG. 4 to turn onor off all of the slave nodes within an all on/off group.

FIGS. 22 a-22 b is a flow chart and schematic illustration of anexemplary embodiment of a method of highlighting a device in the system.

FIGS. 23 a-23 b is a flow chart illustration of an exemplary embodimentof a method of controlling a highlighted in the system.

FIGS. 24 a-24 c is a flow chart illustration of an exemplary embodimentof a method of installing a device in the system.

FIGS. 25 a-25 b is a flow chart illustration of an exemplary embodimentof a method of associating devices in the system.

FIGS. 26 a-26 b is a flow chart illustration of an exemplary embodimentof a method of uninstalling a device from the system.

FIG. 27 is a flow chart illustration of an exemplary embodiment of amethod of removing a device from the system.

FIGS. 28 a-28 d is a flow chart illustration of an exemplary embodimentof a method of replacing a device in the system.

FIGS. 29 a-29 b is a flow chart illustration of an exemplary embodimentof a method of controlling a device in the system.

FIG. 30 is a flow chart illustration of an exemplary embodiment of amethod of selecting child protection for a device in the system.

FIG. 31 is a flow chart illustration of an exemplary embodiment of amethod of renaming a device in the system.

FIGS. 32 a-32 b is a flow chart illustration of an exemplary embodimentof a method of configuring a device in the system.

FIGS. 33 a-33 b is a flow chart and schematic illustration of anexemplary embodiment of a method of viewing the version of a device inthe system.

FIGS. 34 a-34 b is a flow chart illustration of an exemplary embodimentof a method of selecting a level of functionality for all switchoperation of devices in the system.

FIGS. 35 a-35 d is a flow chart and schematic illustration of anexemplary embodiment of a method of creating scenes in the system.

FIG. 36 is a flow chart illustration of an exemplary embodiment of amethod of deleting scenes in the system.

FIGS. 37 a-37 b is a flow chart illustration of an exemplary embodimentof a method of editing scenes in the system.

FIG. 38 is a flow chart illustration of an exemplary embodiment of amethod of activating scenes in the system.

FIG. 39 is a flow chart illustration of an exemplary embodiment of amethod of deactivating scenes in the system.

FIGS. 40 a-40 b is a flow chart and schematic illustration of anexemplary embodiment of a method of creating events in the system.

FIG. 41 is a flow chart illustration of an exemplary embodiment of amethod of deleting events in the system.

FIG. 42 is a flow chart illustration of an exemplary embodiment of amethod of editing events in the system.

FIG. 43 is a flow chart illustration of an exemplary embodiment of amethod of activating events in the system.

FIG. 44 is a flow chart illustration of an exemplary embodiment of amethod of deactivating events in the system.

FIG. 45 is a flow chart illustration of an exemplary embodiment of amethod of selecting a date and time for the system.

FIGS. 46 a-46 b is a flow chart and schematic illustration of anexemplary embodiment of a method of configuring a panic group for thesystem.

FIG. 47 is a flow chart illustration of an exemplary embodiment of amethod of selecting a language for the system.

FIGS. 48 a-48 b is a flow chart and schematic illustration of anexemplary embodiment of a method of displaying a system version for thesystem.

FIGS. 49 a-49 c is a flow chart and schematic illustration of anexemplary embodiment of a method of replicating a configuration of thesystem.

FIGS. 50 a-50 c is a flow chart and schematic illustration of anexemplary embodiment of a method of updating a configuration of thesystem.

FIGS. 51 a-51 b is a flow chart and schematic illustration of anexemplary embodiment of a method of editing an away group of the system.

FIG. 52 is a flow chart illustration of an exemplary embodiment of amethod of activating an away group of the system.

FIG. 53 is a flow chart illustration of an exemplary embodiment of amethod of deactivating an away group of the system.

FIG. 54 is a schematic illustration of an exemplary embodiment of atable top RF controller for the system.

FIG. 54 a is a front view illustration of an exemplary embodiment of thehousing of the table top radio frequency controller.

FIG. 55 is a schematic illustration of an exemplary embodiment of a wallmount RF controller for the system.

FIG. 55 a is a front view illustration of an exemplary embodiment of theinstallation of the wall mount RF controller.

FIG. 56 is a schematic illustration of an exemplary embodiment of a USBRF controller for the system.

FIG. 57 is a schematic illustration of an exemplary embodiment of an RFswitch for the system.

FIG. 57 a is a perspective illustration of an exemplary embodiment ofthe RF switch.

FIG. 58 is a schematic illustration of an exemplary embodiment of thecontroller of the RF switch.

FIG. 59 is a schematic illustration of an exemplary embodiment of thestate engine of the controller of the RF switch.

FIG. 60 is a schematic illustration of an exemplary embodiment of thememory of the RF switch.

FIG. 61 is a schematic illustration of an exemplary embodiment of thedevice database of the memory of the RF switch.

FIG. 62 is a flow chart illustration of an exemplary embodiment of amethod of installation for the RF switch.

FIG. 63 is a flow chart illustration of an exemplary embodiment of amethod of change of state for the RF switch.

FIGS. 64 a and 64 b is a flow chart and schematic illustration of anexemplary embodiment of a method of association for the RF switch.

FIG. 65 is a flow chart illustration of an exemplary embodiment of amethod of child protection for the RF switch.

FIGS. 66 a to 66 c is a flow chart illustration of an exemplaryembodiment of a method of delayed off for the RF switch.

FIGS. 67 a and 67 b is a flow chart illustration of an exemplaryembodiment of a method of panic mode for the RF switch.

FIG. 68 is a flow chart illustration of an exemplary embodiment of amethod of loss of power detection for the RF switch.

FIG. 69 is a schematic illustration of an exemplary embodiment of an RFreceptacle for the system.

FIG. 69 a is a perspective illustration of an exemplary embodiment ofthe RF receptacle.

FIG. 70 is a schematic illustration of an exemplary embodiment of thecontroller of the RF receptacle.

FIG. 71 is a schematic illustration of an exemplary embodiment of thestate engine of the controller of the RF receptacle.

FIG. 72 is a schematic illustration of an exemplary embodiment of thememory of the RF receptacle.

FIG. 73 is a schematic illustration of an exemplary embodiment of thedevice database of the memory of the RF receptacle.

FIG. 74 is a flow chart illustration of an exemplary embodiment of amethod of installation for the RF receptacle.

FIG. 75 is a flow chart illustration of an exemplary embodiment of amethod of turning on the RF receptacle.

FIG. 76 is a flow chart illustration of an exemplary embodiment of amethod of change of state for the RF receptacle.

FIGS. 77 a and 77 b is a flow chart and schematic illustration of anexemplary embodiment of a method of association for the RF receptacle.

FIG. 78 is a flow chart illustration of an exemplary embodiment of amethod of child protection for the RF receptacle.

FIGS. 79 a to 79 c is a flow chart illustration of an exemplaryembodiment of a method of delayed off for the RF receptacle.

FIGS. 80 a and 80 b is a flow chart illustration of an exemplaryembodiment of a method of panic mode for the RF receptacle.

FIG. 81 is a flow chart illustration of an exemplary embodiment of amethod of loss of power detection for the RF receptacle.

FIG. 82 is a schematic illustration of an exemplary embodiment of an RFsmart dimmer for the system.

FIG. 82 a is a perspective illustration of an exemplary embodiment ofthe RF smart dimmer.

FIG. 83 is a schematic illustration of an exemplary embodiment of thecontroller of the RF smart dimmer.

FIG. 84 is a schematic illustration of an exemplary embodiment of thestate engine of the controller of the RF smart dimmer.

FIG. 85 is a schematic illustration of an exemplary embodiment of thememory of the RF smart dimmer.

FIG. 86 is a schematic illustration of an exemplary embodiment of thedevice database of the memory of the RF smart dimmer.

FIG. 87 is a flow chart illustration of an exemplary embodiment of amethod of installation for the RF smart dimmer.

FIG. 88 is a flow chart illustration of an exemplary embodiment of amethod of operating the RF smart dimmer.

FIGS. 89 a-89 b is a flow chart illustration of an exemplary embodimentof a method of operating the RF smart dimmer.

FIGS. 90 a and 90 b is a flow chart of an exemplary embodiment of amethod of operating the RF smart dimmer.

FIG. 91 is a flow chart of an exemplary embodiment of a method ofoperating the RF smart dimmer.

FIGS. 92 a to 92 c is a flow chart illustration of an exemplaryembodiment of a method of delayed off for the RF smart dimmer.

FIGS. 93 a and 93 b is a flow chart and schematic illustration of anexemplary embodiment of a method of association for the RF smart dimmer.

FIG. 94 is a flow chart illustration of an exemplary embodiment of amethod of child protection for the RF smart dimmer.

FIGS. 95 a and 95 b is a flow chart illustration of an exemplaryembodiment of a method of panic mode for the RF smart dimmer.

FIG. 96 is a flow chart illustration of an exemplary embodiment of amethod of loss of power detection for the RF smart dimmer.

FIG. 97 is a schematic illustration of an exemplary embodiment of abattery powered RF switch for the system.

FIG. 98 is a schematic illustration of an exemplary embodiment of thecontroller of the battery powered RF switch.

FIG. 99 is a schematic illustration of an exemplary embodiment of thestate engine of the controller of the battery powered RF switch.

FIG. 100 is a schematic illustration of an exemplary embodiment of thememory of the battery powered RF switch.

FIG. 101 is a schematic illustration of an exemplary embodiment of thedevice database of the memory of the battery powered RF switch.

FIG. 102 is a flow chart illustration of an exemplary embodiment of amethod of installation for the battery powered RF switch.

FIG. 103 is a flow chart illustration of an exemplary embodiment of amethod of change of state for the battery powered RF switch.

FIGS. 104 a and 104 b is a flow chart and schematic illustration of anexemplary embodiment of a method of association for the battery poweredRF switch.

FIG. 105 is a flow chart illustration of an exemplary embodiment of amethod of child protection for the battery powered RF switch.

FIGS. 106 a to 106 c is a flow chart illustration of an exemplaryembodiment of a method of delayed off for the battery powered RF switch.

FIGS. 107 a and 107 b is a flow chart illustration of an exemplaryembodiment of a method of panic mode for the battery powered RF switch.

FIG. 108 is a flow chart illustration of an exemplary embodiment of amethod of loss of power detection for the battery powered RF switch.

FIG. 109 is a schematic illustration of an exemplary embodiment of an RFdimmer for the system.

FIG. 109 a is an illustration of an exemplary embodiment of an RFdimmer.

FIG. 110 is a schematic illustration of an exemplary embodiment of thecontroller of the RF dimmer.

FIG. 111 is a schematic illustration of an exemplary embodiment of thestate engine of the controller of the RF dimmer.

FIG. 112 is a schematic illustration of an exemplary embodiment of thememory of the RF dimmer.

FIG. 113 is a schematic illustration of an exemplary embodiment of thedevice database of the memory of the RF dimmer.

FIG. 114 is a flow chart illustration of an exemplary embodiment of amethod of installation for the RF dimmer.

FIG. 115 is a flow chart illustration of an exemplary embodiment of amethod of operating the RF dimmer.

FIG. 116 is a flow chart illustration of an exemplary embodiment of amethod of operating the RF dimmer.

FIGS. 117 a to 117 c is a flow chart illustration of an exemplaryembodiment of a method of delayed off for the RF dimmer.

FIGS. 118 a and 118 b is a flow chart and schematic illustration of anexemplary embodiment of a method of association for the RF dimmer.

FIG. 119 is a flow chart illustration of an exemplary embodiment of amethod of child protection for the RF dimmer.

FIGS. 120 a and 120 b is a flow chart illustration of an exemplaryembodiment of a method of panic mode for the RF dimmer.

FIG. 121 is a flow chart illustration of an exemplary embodiment of amethod of loss of power detection for the RF dimmer.

FIG. 122 is a schematic illustration of an exemplary embodiment of an RFthermostat.

FIG. 123 is a schematic illustration of an exemplary embodiment of acontrol system.

FIG. 124 is a schematic illustration of the system of FIG. 123.

FIG. 125 is a graphical illustration of an exemplary embodiment of theoperation of the system of FIG. 123.

FIG. 126 is an illustration of an exemplary embodiment of a batterypowered RF switch.

FIG. 127 is an exploded view of the battery powered RF switch of FIG.126.

FIG. 128 is an exploded view of an exemplary embodiment of a method ofmounting the battery powered RF switch of FIG. 126 on a surface.

FIG. 129 is an illustration of an exemplary embodiment of the batterypowered RF switch of FIG. 126 mounted onto a surface.

FIG. 130 is an exploded view of an exemplary embodiment of a method ofmounting the battery powered RF switch of FIG. 126 on a surface.

FIG. 131 is an illustration of an exemplary embodiment of the batterypowered RF switch of FIG. 130 mounted onto a surface.

FIG. 132 is an exploded view of an exemplary embodiment of a method ofmounting the battery powered RF switch of FIG. 126 on a surface.

FIG. 133 is an illustration of an exemplary embodiment of the batterypowered RF switch of FIG. 132 mounted onto a surface.

FIGS. 134 a-134 b is a flow chart illustration of an exemplaryembodiment of a method of associating devices in the system.

DETAILED DESCRIPTION

Referring now to FIG. 1, a control system 100 includes one or moremaster nodes 102 that are adapted to control and monitor the operationof one or more slave nodes 104. In an exemplary embodiment, the masternodes 102 and the slave nodes 104 are operably coupled by one or morecommunication interfaces 106 that may, for example, include one or moreof the following: radio frequency (RF), Internet Protocol (IP), powerline, or other conventional communication interfaces.

Referring now to FIG. 2, in an exemplary embodiment, the master nodes102 may include one or more of the following: a hand held RF controller202, a table top RF controller 204, a wall mounted RF controller 206,and/or a Universal Serial Bus (USB) RF Controller 208.

Referring now to FIG. 3, in an exemplary embodiment, the slave nodes 104may include one or more of the following: an RF switch 302, an RFreceptacle 304, an RF smart dimmer 306, a battery operated RF switch308, an RF dimmer 310, and a thermostat device 312.

Referring now to FIG. 4, in an exemplary embodiment, the hand held RFcontroller 202 includes a controller 402 that is operably coupled to anRF transceiver 404, a memory 406, a network interface 408, a keypad 410,a user interface 412, a display 414, and a battery 416.

In an exemplary embodiment, the controller 402 is adapted to control andmonitor the operation of the RF transceiver 404, the memory 406, thenetwork interface 408, the keypad 410, the user interface 412, thedisplay 414, and the battery 416. In an exemplary embodiment, thecontroller 402 includes one or more of the following: a conventionalprogrammable general purpose controller, an application specificintegrated circuit (ASIC), or other conventional controller devices. Inan exemplary embodiment, the controller 402 includes a model ZW0201controller, commercially available from Zensys A/S.

Referring now to FIG. 5, in an exemplary embodiment, the controller 402includes an operating system 502, application programs 504, and a bootloader 506. In an exemplary embodiment, the operating system 502includes a serial communications driver 502 a, a memory driver 502 b, adisplay driver 502 c, and a button input driver 502 d. In an exemplaryembodiment, the serial communications driver 502 a controls serialcommunications using the RF serial transceiver 404, the memory driver502 b controls the memory 406, the display driver 502 c controls thegeneration of all text and graphics on the display 414, and the buttoninput driver 502 d debounces button inputs provided by a user using thekeypad 410. In an exemplary embodiment, the serial communications driver502 a includes a Z-Wave™ serial API driver that implements a Z-Wave™serial API protocol. The Z-Wave™ serial API driver that implements aZ-Wave™ serial API protocol are both commercially available from ZensysA/S.

In an exemplary embodiment, the application programs 504 include amenu-state engine 504 a. In an exemplary embodiment, the menu-stateengine 504 a permits an operator of the hand held RF controller 202 tocustomize the operation of the system 100.

Referring now to FIG. 6, in an exemplary embodiment, the menu stateengine 504 a includes a device engine 602 a, a scenes engine 602 b, anevents engine 602 c, a system engine 602 d, and an away engine 603 e.

In an exemplary embodiment, the device engine 602 a permits the operatorof the hand held RF controller 202 to customize the operation of atleast some of the aspects of the master and slave nodes, 102 and 104,respectively. In an exemplary embodiment, the device engine 602 aincludes a device install engine 602 aa, a device associate engine 602ab, a device uninstall engine 602 ac, a device remove engine 602 ad, adevice replace engine 602 ae, a device control engine 602 af, a devicechild protection engine 602 ag, a device rename engine 602 ah, a deviceconfigure engine 602 ai, a device version engine 602 aj, and a deviceall switch engine 602 ak.

In an exemplary embodiment, the device install engine 602 aa permits anoperator of the hand held RF controller 202 to install one or moremaster and/or slave nodes, 102 and 104, respectively, into the system100. In an exemplary embodiment, as illustrated in FIG. 7, the deviceassociate engine 602 ab permits the operator of the hand held RFcontroller 202 to associate one or more master and/or slave nodes, 102and 104, with one another to thereby define a communication pathway 702that includes the associated nodes, e.g., 704 a and 704 b. As a result,communications between a source node 706 and a destination node 708within the system 100 may employ the defined pathway 702.

In an exemplary embodiment, the device uninstall engine 602 ac permitsan operator of the hand held RF controller 202 to uninstall one or moremaster and/or slave nodes, 102 and 104, respectively, out of the system100. In an exemplary embodiment, the device remove engine 602 ad permitsan operator of the hand held RF controller 202 to remove one or moremaster and/or slave nodes, 102 and 104, respectively, from the system100.

In an exemplary embodiment, the device replace engine 602 ae permits anoperator of the hand held RF controller 202 to replace one or moremaster and/or slave nodes, 102 and 104, respectively, with other masterand/or slave nodes in the system 100. In an exemplary embodiment, thedevice control engine 602 af permits an operator of the hand held RFcontroller 202 to control one or more master and/or slave nodes, 102 and104, respectively, in the system 100.

In an exemplary embodiment, the device child protection engine 602 agpermits an operator of the hand held RF controller 202 to define thelevel of child protection for one or more master and/or slave nodes, 102and 104, respectively, in the system 100. In an exemplary embodiment,the device rename engine 602 ah permits an operator of the hand held RFcontroller 202 to rename one or more master and/or slave nodes, 102 and104, respectively, in the system 100.

In an exemplary embodiment, the device configure engine 602 ai permitsan operator of the hand held RF controller 202 to configure one or moremaster and/or slave nodes, 102 and 104, respectively, in the system 100.In an exemplary embodiment, the device version engine 602 aj, permits anoperator of the hand held RF controller 202 to determine and/orconfigure the version of one or more master and/or slave nodes, 102 and104, respectively, in the system 100.

In an exemplary embodiment, the device all switch engine 602 ak permitsan operator of the hand held RF controller 202 to define and configurethe operation of the master and/or slave nodes, 102 and 104,respectively, to be included in an all switch group defined within thesystem 100.

In an exemplary embodiment, as illustrated in FIG. 8, the scenes engine602 b permits the operator of the hand held RF controller 202 tocustomize, define, and otherwise control the operation of one or morescenes, e.g., 802 a-802 f, using one or more of the slave nodes 102 inthe system 100. In an exemplary embodiment, as illustrated in FIG. 9,each scene 802 defines the operating states, e.g., 904 a-904 f one ormore corresponding slave nodes 102 a-102 f, in the system 100.

In an exemplary embodiment, the scenes engine 602 b includes a scenescreate engine 602 ba, a scenes delete engine 602 bb, a scenes editengine 602 bc, a scenes activate engine 602 bd, and a scenes deactivateengine 602 be.

In an exemplary embodiment, the scenes create engine 602 ba permits anoperator of the hand held RF controller 202 to create one or more scenes802 in the system 100. In an exemplary embodiment, the scenes deleteengine 602 bb permits an operator of the hand held RF controller 202 todelete one or more scenes 802 from the system 100.

In an exemplary embodiment, the scenes edit engine 602 bc permits anoperator of the hand held RF controller 202 to edit one or more scenes802 in the system 100. In an exemplary embodiment, the scenes activateengine 602 bd permits an operator of the hand held RF controller 202 toactivate one or more scenes 802 in the system 100. In an exemplaryembodiment, the scenes deactivate engine 602 be permits an operator ofthe hand held RF controller 202 to deactivate one or more scenes 802 inthe system 100.

In an exemplary embodiment, as illustrated in FIG. 10, the events engine602 c permits the operator of the hand held RF controller 202 tocustomize, define, and otherwise control the operation of one or moreevents, e.g., 1002 a-1002 d, using one or more of the slave nodes 102 inthe system 100. In an exemplary embodiment, as illustrated in FIG. 11,each event 1002 includes a time of occurrence 1102, a day of occurrence1104, an event type 1106, the scene to be used in the event 1108, andwhether the event is active or inactive 1110.

In an exemplary embodiment, the events engine 602 c includes an eventscreate engine 602 ca, an events delete engine 602 cb, an events editengine 602 cc, an events activate engine 602 cd, and an eventsdeactivate engine 602 ce.

In an exemplary embodiment, the events create engine 602 ca permits anoperator of the hand held RF controller 202 to create one or more events1002 in the system 100. In an exemplary embodiment, the events deleteengine 602 cb permits an operator of the hand held RF controller 202 todelete one or more events 1002 from the system 100.

In an exemplary embodiment, the events edit engine 602 cc permits anoperator of the hand held RF controller 202 to edit one or more events1002 in the system 100. In an exemplary embodiment, the events activateengine 602 cd permits an operator of the hand held RF controller 202 toactivate one or more events 1002 in the system 100. In an exemplaryembodiment, the events deactivate engine 602 ce permits an operator ofthe hand held RF controller 202 to deactivate one or more events 1002 inthe system 100.

In an exemplary embodiment, the system engine 602 d includes a systemdate/time engine 602 da, a system panic engine 602 db, a system languageengine 602 dc, a system version engine 602 dd, a system replicate engine602 de, and a system update engine 602 df.

In an exemplary embodiment, the system date/time engine 602 da permitsan operator of the hand held RF controller 202 to enter and/or edit thedate and time of the system 100.

In an exemplary embodiment, as illustrated in FIG. 12, the system panicengine 602 db permits an operator of the hand held RF controller 202 todefine a panic group 1202 within the system 100. In an exemplaryembodiment, as illustrated in FIG. 13, the panic group 1202 includes oneor more slave nodes 104 and corresponding panic modes of operation 1302for each of the slave nodes included in the panic group 1202.

In an exemplary embodiment, the system language engine 602 dc permits anoperator of the hand held RF controller 202 to define the language to beused in the system 100. In an exemplary embodiment, the system versionengine 602 dd permits an operator of the hand held RF controller 202 toview the system version of the system 100 on, for example, the display414.

In an exemplary embodiment, the system replicate engine 602 de permitsan operator of the hand held RF controller 202 to replicate one or moreaspects of the hand held RF controller into another master node 102 tobe used in the system 100. In an exemplary embodiment, the system updateengine 602 df permits an operator of the hand held RF controller 202 toupdate one or more aspects of the operating system 502 or applicationprograms 504 to be used in the system 100.

In an exemplary embodiment, as illustrated in FIG. 14, the away engine602 e permits an operator of the hand held RF controller 202 to definean away group 1402 within the system 100. In an exemplary embodiment, asillustrated in FIG. 15, the away group 1402 includes one or more slavenodes 104 and corresponding away modes of operation 1502 for each of theslave nodes included in the away group 1402.

In an exemplary embodiment, the away engine 602 e includes an away groupedit engine 602 ea, an away group activate engine 602 eb, and an awaygroup deactivate engine 602 ec.

In an exemplary embodiment, the away group edit engine 602 ea permits anoperator of the hand held RF controller 202 to edit one or more aspectsof the away group 1402 to be used in the system 100. In an exemplaryembodiment, the away group activate engine 602 eb permits an operator ofthe hand held RF controller 202 to activate one or more aspects of theaway group 1402 used in the system 100. In an exemplary embodiment, theaway group deactivate engine 602 ec permits an operator of the hand heldRF controller 202 to deactivate one or more aspects of the away group1402 used in the system 100.

In an exemplary embodiment, the RF transceiver 404 is operably coupledto and controlled by the controller 402. In an exemplary embodiment, theRF transceiver 404 transmits and receives RF communications to and fromother master and slave nodes, 102 and 104, respectively. In an exemplaryembodiment, the RF transceiver 404 may, for example, include one or moreof the following: a conventional RF transceiver, and/or the model ZW0201RF transceiver commercially available from Zensys A/S.

In an exemplary embodiment, the memory 406 is operably coupled to andcontrolled by the controller 402. In an exemplary embodiment, asillustrated in FIG. 16, the memory 406 includes a copy of the operatingsystem 1602, a copy of the application programs 1604, a devices database1606, scenes database 1608, an events database 1610, a system database1612, an away database 1614, a communications pathway database 1616, anda failed node ID listing 1618. In an exemplary embodiment, the memory406 includes a model 24LC256 non volatile memory, commercially availablefrom Microchip.

In an exemplary embodiment, as illustrated in FIGS. 17 and 18, thedevices database 1606 includes a node information frame 1702 for each ofthe nodes in the system 100 that each include a generic device class1802, a specific device class 1804, a command class 1806, a protectioncommand class 1808, a version command class 1810, a manufacturingproprietary command class 1810, and an all switch command class 1812. Inan exemplary embodiment, the devices database 1606 includes databaseinformation used by at least the devices engine 602 a.

In an exemplary embodiment, the scenes database 1608 includes databaseinformation used by at least the scenes engine 602 b. In an exemplaryembodiment, the events database 1610 includes database information usedby at least the events engine 602 c. In an exemplary embodiment, thesystem database 1612 includes database information used by at least thesystem engine 602 d. In an exemplary embodiment, the away database 1614includes database information used by at least the away engine 602 e.

In an exemplary embodiment, the communications pathway database 1616includes database information regarding the communication pathways 702,and the failed node ID listing 1618 includes information regarding themaster and slave nodes, 102 and 104, respectively, that have failed inthe system 100.

In an exemplary embodiment, the network interface 408 is operablycoupled to and controlled and monitored by the controller 402. In anexemplary embodiment, the network interface 408 permits the hand held RFcontroller 202 to communicate with external devices via conventionalcommunication interfaces such as, for example, internet protocol.

In an exemplary embodiment, the keypad 410 is operably coupled to andcontrolled and monitored by the controller 402. In an exemplaryembodiment, the keypad 410 permits a user of the hand held RF controller202 to input information into the controller to thereby control theoperation of the controller. In an exemplary embodiment, as illustratedin FIG. 19, the keypad 410 includes an alpha-numeric keypad 1902,navigation buttons 1904, an OK button 1906, a BACK button 1908, one ormore user programmable HOT BUTTONS 1910, ON button 1912 a, OFF button1912 b, a PANIC button 1914, and one or more user programmable MENU KEYS1916.

In an exemplary embodiment, the user interface 412 is operably coupledto and controlled and monitored by the controller 402. In an exemplaryembodiment, the user interface 412 permits a user of the hand held RFcontroller 202 to interface with the controller to thereby monitor andcontrol the operation of the controller.

In an exemplary embodiment, the display 414 is operably coupled to andcontrolled and monitored by the controller 402. In an exemplaryembodiment, the display 414 permits a user of the hand held RFcontroller 202 to interface with the controller to thereby monitor andcontrol the operation of the controller. In an exemplary embodiment, thedisplay 414 includes a model JCM13064D display, commercially availablefrom Jinghua.

In an exemplary embodiment, the battery 416 provides electrical powerfor and is operably coupled to all of the elements of the hand held RFcontroller 202.

In an exemplary embodiment, as illustrated in FIGS. 19 a and 19 b, theelements of the hand held RF controller 202 may be positioned within andsupported by a housing 1920 having a cover 1922 that defines one or moreopenings for the keypad 410, including one or more of the alpha-numerickeypad 1902, the navigation buttons 1904, the OK button 1906, the BACKbutton 1908, the ALL ON button 1912 a, the ALL OFF button 1912 b, thePANIC button 1914, and the MENU keys 1916, and the display 414.

Referring now to FIG. 20, in an exemplary embodiment, during theoperation of the hand held RF controller 202, the controller implementsa menu-based program 2000 having a main menu 2002 in which a user of thehand held RF controller may initially select: DEVICES 2004, SCENES 2006,EVENTS 2008, SYSTEM 2010, or AWAY 2012 using the keypad 410.

In an exemplary embodiment, user selection of DEVICES 2004 permits theuser to control, monitor and/or configure one or more aspects of themaster and slave nodes, 102 and 104, respectively of the system 100using the device engine 602 a. In an exemplary embodiment, userselection of SCENES 2006 permits the user to control, monitor, and/orconfigure one or more aspects of the scenes 802 of the system 100 usingthe scenes engine 602 b. In an exemplary embodiment, user selection ofEVENTS 2008 permits the user to control, monitor, and/or configure oneor more aspects of the events 1002 of the system 100 using the eventengine 602 c. In an exemplary embodiment, user selection of SYSTEM 2010permits the user to control, monitor, and/or configure one or moreaspects of the system 100 using the system engine 602 d. In an exemplaryembodiment, user selection of AWAY 2012 permits the user to control,monitor, and/or configure one or more aspects of the away group 1402 ofthe system 100 using the away engine 602 e.

After selecting DEVICES 2004, the user of the hand held RF controller202 may then select: INSTALL 2004 a, ASSOCIATE 2004 b, UNINSTALL 2004 c,REMOVE 2004 d, REPLACE 2004 e, CONTROL 2004 f, CHILD PROTECTION 2004 g,RENAME 2004 h, CONFIGURE 2004 i, VERSION 2004 j, or ALL SWITCH 2004 k.In an exemplary embodiment, user selection of: a) INSTALL 2004 a, b)ASSOCIATE 2004 b, c) UNINSTALL 2004 c, d) REMOVE 2004 d, e) REPLACE 2004e, f) CONTROL 2004 f, g) CHILD PROTECTION 2004 g, h) RENAME 2004 h, i)CONFIGURE 2004 i, j) VERSION 2004 j, or k) ALL SWITCH 2004 k permits theuser to control, monitor, and/or configure one or more aspects of: a)the installation of master and/or slave nodes, 102 and 104,respectively; b) the association of slave nodes; c) the uninstallationof master and/or slave nodes; d) the removal of master and/or slavenodes; e) the replacement of master and/or slave nodes; f) the controlof master and/or slave nodes; g) child protection for master and/orslave nodes; h) renaming master and/or slave nodes; i) configuringmaster and/or slave nodes; j) controlling, editing, and monitoring theversion of master and/or slave nodes; or k) configuring and controllingthe slave nodes in the all switch group, respectively, in the system 100using the devices engine 602 a.

After selecting SCENES 2006, the user of the hand held RF controller 202may then select: CREATE 2006 a, DELETE 2006 b, EDIT 2006 c, ACTIVATE2006 d, or DEACTIVATE 2006 e. In an exemplary embodiment, user selectionof a) CREATE 2006 a, b) DELETE 2006 b, c) EDIT 2006 c, d) ACTIVATE 2006d, or e) DEACTIVATE 2006 e permits the user to control, monitor, and/orconfigure one or more aspects of: a) creating scenes 802; b) deletingscenes; c) editing scenes; d) activating scenes; or e) deactivatingscenes, respectively, in the system 100 using the scenes engine 602 b.

After selecting EVENTS 2008, the user of the hand held RF controller 202may then select: CREATE 2008 a, DELETE 2008 b, EDIT 2008 c, ACTIVATE2008 d, or DEACTIVATE 2008 e. In an exemplary embodiment, user selectionof a) CREATE 2008 a, b) DELETE 2008 b, c) EDIT 2008 c, d) ACTIVATE 2008d, or e) DEACTIVATE 2008 e permits the user to control, monitor, and/orconfigure one or more aspects of: a) creating events 1002; b) deletingevents; c) editing events; d) activating events; or e) deactivatingevents, respectively, in the system 100 using the event engine 602 c.

After selecting SYSTEM 2010, the user of the hand held RF controller 202may then select: DATE/TIME 2010 a, PANIC 2010 b, LANGUAGE 2010 c,VERSION 2010 d, REPLICATE 2010 e, or UPDATE 2010 f. In an exemplaryembodiment, user selection of a) DATE/TIME 2010 a, b) PANIC 2010 b, c)LANGUAGE 2010 c, d) VERSION 2010 d, e) REPLICATE 2010 e, or f) UPDATE2010 f permits the user to control, monitor, and/or configure one ormore aspects of: a) the date and time for the system 100; b) theconfiguration and operation of the panic group 1202; c) the languageused in the system; d) the version of one or more aspects of the system;e) replicating master and/or slave nodes, or f) updating one or moreaspects of the system, respectively, in the system using the systemengine 602 d.

After selecting AWAY 2012, the user of the hand held RF controller 202may then select: EDIT 2012 a, ACTIVATE 2012 b, or DEACTIVATE 2012 c. Inan exemplary embodiment, user selection of a) EDIT 2012 a, b) ACTIVATE2012 b, or c) DEACTIVATE 2012 c permits the user to control, monitor,and/or configure one or more aspects of: a) the configuration andoperation of the away group 1402; b) activation of the away group; or c)deactivation of the away group, respectively, in the system using theaway engine 602 e.

Referring now to FIG. 21, in an exemplary embodiment, during theoperation of the hand held RF controller 202, the controller implementsa method 2100 in which all of the slave nodes 104, within a user definedall on/off group, may be turned on or off. In particular, in step 2102,the controller 302 determines if the ON button 1912 a has been depressedby the user. If the ON button 1912 has been depressed by the user, thecontroller 302 turns on all of the slave nodes 104 within the all on/offgroup in step 2104. Alternatively, if the controller determines that theOFF button 1912 b has been depressed by the user in step 2106, then thecontroller 302 turns off all of the slave nodes 104 within the allon/off group in step 2108. In this manner, the hand held RF controller202 may control the operation of all of the slave nodes 104 includedwithin the all on/off group.

Referring now to FIGS. 22 a and 22 b, in an exemplary embodiment, duringthe operation of the hand held RF controller 202, the controllerimplements a method 2200 in which the controller determines if a numericbutton has been depressed on the keypad 1902 by a user in step 2202. Ifa numeric button has been depressed on the keypad 1902 by a user, then adevice access display screen 2204 is displayed on the display 414 thatincludes a highlighted device 2206 that corresponds to the numericbutton depressed highlighted in step 2208. In this manner, the hand heldRF controller 202 permits a user to quickly and efficiently select, viewand/or edit the configuration and operational details for a particularmaster and slave node, 102 and 104, respectively.

Referring now to FIGS. 23 a and 23 b, in an exemplary embodiment, duringthe operation of the hand held RF controller 202, after highlighting aselected device using the method 2200, the controller implements amethod 2300 in which the controller determines if a highlighted device2206 has been selected on the display 414 in step 2302. If a highlighteddevice 2206 has been selected, the hand held RF controller 202 thendetermines if the ON or OFF buttons, 1912 a or 1912 b, respectively,have been depressed on the keypad 410 by a user in step 2304. If the ONor OFF buttons, 1912 a or 1912 b, respectively, have been depressed onthe keypad 410 by a user, then the hand held RF controller 202 thendetermines if the highlighted device 2206 supports on or off operationalstates in step 2306. If the highlighted device 2206 does not support onor off operational states, then the hand held RF controller 202 promptsthe user to enter a value for the desired operational state of thehighlighted device 2206 in step 2308. For example, if the highlighteddevice 2206 is a thermostat, the hand held RF controller 202 may promptthe user for the desired temperature setting and/or whether airconditioning or heating is desired.

Alternatively, if the highlighted device 2206 does support on or offoperational states, then the hand held RF controller 202 determines ifthe highlighted device 2206 supports dimming or brightening operationalstates in step 2310. If the highlighted device 2206 supports dimming orbrightening operational states, then the hand held RF controller 202determines if the ON or OFF button, 1912 a or 1912 b, respectively, weredepressed by a user for predetermined minimum time period in step 2312.If the ON or OFF button, 1912 a or 1912 b, respectively, were depressedby a user for predetermined minimum time period, then the hand held RFcontroller 202 brightens or dims the highlighted device 2206 in step2314. Alternatively, if the ON or OFF button, 1912 a or 1912 b,respectively, were not depressed by a user for predetermined minimumtime period, then the hand held RF controller 202 determines if thehighlighted device 2206 permits a delay in turning the device on or offin step 2316. If the highlighted device 2206 permits a delay in turningthe device on or off, then the hand held RF controller 202 turns thedevice on or off with a predetermined time delay in step 2318.Alternatively, if the highlighted device 2206 does not permit a delay inturning the device on or off, then the hand held RF controller 202 turnsthe device on or off without a predetermined time delay in step 2320.

Alternatively, if the highlighted device 2206 does not support dimmingor brightening operational states, then the hand held RF controller 202determines if the highlighted device 2206 permits a delay in turning thedevice on or off in step 2322. If the highlighted device 2206 permits adelay in turning the device on or off, then the hand held RF controller202 turns the device on or off with a predetermined time delay in step2324. Alternatively, if the highlighted device 2206 does not permit adelay in turning the device on or off, then the hand held RF controller202 turns the device on or off without a predetermined time delay instep 2326. In this manner, the hand held RF controller 202 permits auser to quickly and efficiently control the operational state of aparticular slave node 104, and thereby control the operational state ofthe highlighted device 2206 by: a) turning the device on or off withouta time delay; b) turning the device on or off with a time delay; or c)brighten or dim the device.

Referring now to FIGS. 24 a-24 c, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and INSTALL 2004 a, using the menu-based program2000, the controller implements a method 2400 in which the controllerpermits a user to install one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, in the system 100. Inparticular, in step 2402 the hand held RF controller 202 determines if auser has selected the installation of a device in the system 100. If theuser has selected the installation of device in the system 100, then thedisplay 414 of the hand held RF controller 202 prompts the user to pressthe install button on the device to be installed in the system in step2404. Depression of the install button on the device to be installed inthe system 100 will cause the device to be installed in the system totransmit the node information frame 1702 for the device to the hand heldRF controller 202.

If the node information frame 1702 for the device to be installed in thesystem 100 is received by the hand held RF controller 202 in step 2406,then the controller will permit the installation of the device toproceed in step 2408. As part of the installation of the device into thesystem 100, the hand held RF controller 202 will also scan the nodeinformation frame 1702 for the device to be installed in the system 100in step 2410.

Alternatively, if the node information frame 1702 for the device to beinstalled in the system 100 is not received by the hand held RFcontroller 202 in step 2406, then the controller will determine if theinstallation of the device has been canceled by the user in step 2412.If the hand held RF controller 202 determines that the installation ofthe device has been canceled by the user, then the controller willdisplay an installation cancellation message on the display 414 in step2414. If the hand held RF controller 202 determines that theinstallation of the device has not been canceled by the user in step2412, then the controller will determine if a predetermined timeout hasoccurred in step 2416. If the hand held RF controller 202 determinesthat a predetermined timeout has occurred, then the controller willdisplay an installation cancellation message on the display 414 in step2414.

If the hand held RF controller 202 determines that the installation ofthe device in steps 2408 and 2410 did not occur within a predeterminedtimeout in step 2418, then the controller will display an installationcancellation message on the display 414 in step 2414. Alternatively, ifthe hand held RF controller 202 determines that the installation of thedevice in steps 2408 and 2410 did occur within a predetermined timeoutin step 2418, then the controller will determine if the installed devicecan be a static controller by interrogating the node information frame1702 for the installed device in step 2420.

If the hand held RF controller 202 determines that the installed devicecan be a static controller in step 2420, then the controller willdetermine if the installed device can be a system information server byinterrogating the node information frame 1702 for the installed devicein step 2422. If the hand held RF controller 202 determines that theinstalled device can be a system information server in step 2422, thenthe controller will designate the installed device as a systeminformation server for the system 100 in step 2424. When the installeddevice provides a system information server, it stores a record of theconfiguration and operational details of the system 100. As a result, itprovides an archival back-up record of the design and operation of thesystem 100.

If: a) the hand held RF controller 202 determines that the installeddevice cannot be a static controller in step 2420, b) the controllerdetermines that the installed device cannot be a system informationserver in step 2422, or c) after completing step 2424, the controllerdetermines if the installed device supports an all switch command classin step 2426. If the hand held RF controller 202 determines that theinstalled device supports an all switch command class in step 2426, thenthe controller adds the installed device to the away group 1402 in step2428.

Referring now to FIGS. 25 a-25 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and ASSOCIATE 2004 b, using the menu-based program2000, the controller implements a method 2500 in which the controllerpermits a user to associate devices, such as, for example, master andslave nodes, 102 and 104, respectively, to define a communicationpathway 702 within the system 100. In particular, in step 2502 the handheld RF controller 202 determines if a user has selected the associationof a device in the system 100 with a communication pathway 702. If theuser has selected the association of device in the system 100 with acommunication pathway 702, then the display 414 of the hand held RFcontroller 202 prompts the user to press the associate button on thedevice to be designated as a destination node 708 within a communicationpathway in the system in step 2504. Depression of the associate buttonon the device to be designated as a destination node 708 within acommunication pathway 702 in the system 100 will cause the device totransmit the node information frame 1702 for the device to the hand heldRF controller 202.

If the node information frame 1702 for the device to be designated as adestination node 708 within a communication pathway 702 in the system100 is received by the hand held RF controller 202 in step 2506, thenthe display 414 of the hand held RF controller 202 prompts the user topress the associate button on the device to be designated as a sourcenode 706 within a communication pathway 702 in the system 100 in step2508. If the node information frame 1702 for the device to be designatedas a source node 706 within a communication pathway 702 in the system100 is received by the hand held RF controller 202 in step 2510, thenthe sequentially associated nodes are associated with one another in thecommunication pathway 702 and designated as destination and sourcenodes, 708 and 706, respectively, in step 2512.

Alternatively, if the node information frame 1702 for the device to bedesignated as a destination node 708 within the communication pathway702 in the system 100 is not received by the hand held RF controller 202in step 2506, then the controller determines if a user has cancelled theassociation in step 2514. If the hand held RF controller 202 determinesthat a user has cancelled the association, then the association iscancelled in step 2516.

Referring now to FIGS. 26 a-26 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and UNINSTALL 2004 c, using the menu-based program2000, the controller implements a method 2600 in which the controllerpermits a user to uninstall one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, from the system 100.In particular, in step 2602 the hand held RF controller 202 determinesif a user has selected the uninstallation of a device from the system100. If the user has selected the uninstallation of device from thesystem 100, then the display 414 of the hand held RF controller 202prompts the user to press the uninstall button on the device to beuninstalled from the system in step 2604. Depression of the uninstallbutton on the device to be uninstalled in the system 100 will cause thedevice to be uninstalled in the system to transmit the node informationframe 1702 for the device to the hand held RF controller 202.

If the node information frame 1702 for the device to be uninstalled inthe system 100 is received by the hand held RF controller 202 in step2606, then the controller will permit the uninstallation of the devicefrom the system 100 to proceed in step 2608.

Alternatively, if the node information frame 1702 for the device to beuninstalled from the system 100 is not received by the hand held RFcontroller 202 in step 2606, then the controller will determine if theuninstallation of the device has been canceled by the user in step 2610.If the hand held RF controller 202 determines that the uninstallation ofthe device has been canceled by the user, then the controller willcancel the uninstallation in step 2612. If the hand held RF controller202 determines that the uninstallation of the device has not beencanceled by the user in step 2610, then the controller will determine ifa predetermined timeout has occurred in step 2614. If the hand held RFcontroller 202 determines that a predetermined timeout has occurred,then the controller will cancel the uninstallation in step 2612.

If the hand held RF controller 202 determines that the uninstallation ofthe device in steps 2606 and 2608 did not occur within a predeterminedtimeout in step 2616, then the controller will cancel the uninstallationin step 2612. Alternatively, if the hand held RF controller 202determines that the uninstallation of the device in steps 2606 and 2608did occur within a predetermined timeout in step 2616, then thecontroller will uninstall the device from the system 100 in step 2618.

Referring now to FIG. 27, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and REMOVE 2004 d, using the menu-based program2000, the controller implements a method 2600 in which the controllerpermits a user to remove one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, from the system 100.In particular, in step 2702 the hand held RF controller 202 determinesif a user has selected the removal of a device from the system 100. Ifthe user has selected the removal of device from the system 100, thenthe display 414 of the hand held RF controller 202 prompts the user toselect the device to be removed from the system in step 2704.

If the hand held RF controller 202 determines that the device selectedby a user for removal from the system 100 is listed in the failed nodeID listing 1618 in step 2706, then the device is removed from the systemin step 2708. Alternatively, if the hand held RF controller 202determines that the device selected by a user for removal from thesystem 100 is not listed in the failed node ID listing 1618 in step2706, then the removal of the device is canceled in step 2710.

Referring now to FIGS. 28 a-28 d, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and REPLACE 2004 e, using the menu-based program2000, the controller implements a method 2800 in which the controllerpermits a user to replace one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, with one or moreother devices, such as, for example, master and slave nodes, 102 and104, respectively, within the system 100. In particular, in step 2802the hand held RF controller 202 determines if a user has selected thereplacement of a device within the system 100. If the user has selectedthe replacement of device within the system 100, then the display 414 ofthe hand held RF controller 202 prompts the user to select the device tobe replaced within the system in step 2804.

If the hand held RF controller 202 determines that the device selectedby a user for replacement within the system 100 is listed in the failednode ID listing 1618 in step 2806, then the device may be replacedwithin the system in step 2808. Alternatively, if the hand held RFcontroller 202 determines that the device selected by a user forreplacement within the system 100 is not listed in the failed node IDlisting 1618 in step 2806, then the replacement of the device iscanceled in step 2810.

If the device may be replaced within the system in step 2808, then thedisplay 414 of the hand held RF controller 202 prompts the user to pressthe install button on the replacement device to be installed in thesystem in step 2812. Depression of the install button on the replacementdevice to be installed in the system 100 will cause the replacementdevice to be installed in the system to transmit the node informationframe 1702 for the device to the hand held RF controller 202.

If the node information frame 1702 for the replacement device to beinstalled in the system 100 is received by the hand held RF controller202 in step 2814, then the controller will permit the installation ofthe replacement device to proceed in step 2816. As part of theinstallation of the device into the system 100, the hand held RFcontroller 202 will also scan the node information frame 1702 for thereplacement device to be installed in the system 100 in step 2818.

Alternatively, if the node information frame 1702 for the replacementdevice to be installed in the system 100 is not received by the handheld RF controller 202 in step 2814, then the controller will determineif the installation of the replacement device has been canceled by auser in step 2820. If the hand held RF controller 202 determines thatthe installation of the replacement device has been canceled by a user,then the controller will cancel the replacement in step 2822. If thehand held RF controller 202 determines that the installation of thereplacement device has not been canceled by a user in step 2820, thenthe controller will determine if a predetermined timeout has occurred instep 2824. If the hand held RF controller 202 determines that apredetermined timeout has occurred, then the controller will cancel thereplacement in step 2822.

If the hand held RF controller 202 determines that the installation ofthe replacement device in steps 2816 and 2818 did not occur within apredetermined timeout in step 2826, then the controller will cancel thereplacement in step 2822. Alternatively, if the hand held RF controller202 determines that the installation of the replacement device in steps2816 and 2818 did occur within a predetermined timeout in step 2826,then the controller will determine if the installed replacement devicecan be a static controller by interrogating the node information frame1702 for the installed replacement device in step 2828.

If the hand held RF controller 202 determines that the installedreplacement device can be a static controller in step 2828, then thecontroller will determine if the installed device can be a systeminformation server by interrogating the node information frame 1702 forthe installed replacement device in step 2830. If the hand held RFcontroller 202 determines that the installed replacement device can be asystem information server in step 2830, then the controller willdesignate the installed replacement device as a system informationserver for the system 100 in step 2832. When the installed replacementdevice provides a system information server, it stores a record of theconfiguration and operational details of the system 100. As a result, itprovides an archival back-up record of the design and operation of thesystem 100.

If: a) the hand held RF controller 202 determines that the installedreplacement device cannot be a static controller in step 2828, b) thecontroller determines that the installed replacement device cannot be asystem information server in step 2830, or c) after completing step2832, the controller determines if the installed replacement devicesupports an all switch command class in step 2834. If the hand held RFcontroller 202 determines that the installed replacement device supportsan all switch command class in step 2834, then the controller adds theinstalled replacement device to the away group 1402 in step 2836.

Referring now to FIGS. 29 a-29 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and CONTROL 2004 f, using the menu-based program2000, the controller implements a method 2900 in which the controllerpermits a user to control one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, within the system100. In particular, in step 2902 the hand held RF controller 202determines if a user has selected the control of a device within thesystem 100. If the user has selected the control of a device within thesystem 100, then the display 414 of the hand held RF controller 202prompts the user to select the device to be controlled within the systemin step 2904.

Once a user of the hand held RF controller 202 has selected the deviceto be controlled, the node data for the selected device is thenretrieved by the controller. In and exemplary embodiment, the node datafor the selected device includes the node information frame 1702 for theselected device. If the node data for the selected device is retrievedby the hand held RF controller 202 within a predetermined time outperiod in step 2906, then the controller examines the node data for theselected device in step 2908. Alternatively, if the node data for theselected device is not retrieved by the hand held RF controller 202within a predetermined time out period in step 2906, then the controllercancels the control of the selected device in step 2910 and displays anerror message on the display 414 in step 2912.

After examining the node data for the selected device in step 2908, thehand held RF controller 202 then determines if the selected device iscontrollable in step 2914. If the hand held RF controller 202 determinesthat the selected device is controllable, the controller then determinesif the command class for the selected device is one recognized by thesystem 100 in step 2916. If the command class for the selected device isone recognized by the system 100, then the hand held RF controller 202will use the command class for the selected device to control theselected device in step 2918. Alternatively, if the command class forthe selected device is not one recognized by the system 100, then thehand held RF controller 202 will use a basic command class for theselected device to control the selected device in step 2920.

Alternatively, if, after examining the node data for the selected devicein step 2908, the hand held RF controller 202 then determines if theselected device is not controllable in step 2914, then the controllercancels the control of the selected device in step 2922 and displays anerror message on the display 414 in step 2924.

Referring now to FIG. 30, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and CHILD PROTECTION 2004 g, using the menu-basedprogram 2000, the controller implements a method 3000 in which thecontroller permits a user to control the level of child protection forone or more devices, such as, for example, master and slave nodes, 102and 104, respectively, within the system 100. In particular, in step3002 the hand held RF controller 202 determines if a user has selectedthe control of a device within the system 100. If the user has selectedthe control the level of child protection of device within the system100, then the display 414 of the hand held RF controller 202 prompts theuser to select the device for which the level of child protection willbe controlled within the system in step 3004.

Once a user of the hand held RF controller 202 has selected the devicefor which the level of child protection will be controlled, the nodedata for the selected device is then retrieved by the controller. In anexemplary embodiment, the node data for the selected device includes thenode information frame 1702 for the selected device. If the node datafor the selected device is retrieved by the hand held RF controller 202within a predetermined time out period in step 3006, then the controllerpermits a user to select the level of child protection for the selecteddevice in step 3008.

In an exemplary embodiment, the possible levels of child protection thatmay be selected in step 3008 may include one or more of thefollowing: 1) no child protection; 2) sequence child protection; and/or3) remote control child protection. In an exemplary embodiment, no childprotection is the default level of child protection. In an exemplaryembodiment, sequence child protection requires a user of a device todepress one or push buttons provided on the device in a predeterminedsequence within a predetermined time period in order to enable the useto adjust an operating state of the device. In an exemplary embodiment,sequence child protection requires a user of a device to depress a pushbutton provided on the device three times in a row within two seconds inorder to enable the use to adjust an operating state of the device. Inan exemplary embodiment, remote control child protection only permits auser to change an operational state of a device by using the hand heldRF controller 202.

Alternatively, if the node data for the selected device is not retrievedby the hand held RF controller 202 within a predetermined time outperiod in step 3006, then the controller cancels the control of thelevel of child protection for the selected device in step 3010 anddisplays an error message on the display 414 in step 3012.

Referring now to FIG. 31, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and RENAME 2004 h, using the menu-based program2000, the controller implements a method 3100 in which the controllerpermits a user to rename one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, within the system100. In particular, in step 3102 the hand held RF controller 202determines if a user has selected the renaming of a device within thesystem 100. If the user has selected the renaming of a device within thesystem 100, then the display 414 of the hand held RF controller 202prompts the user to select the device to be renamed within the system instep 3104.

Once a user of the hand held RF controller 202 has selected the devicethat will be renamed, the node data for the selected device is thenretrieved by the controller. In an exemplary embodiment, the node datafor the selected device includes the node information frame 1702 for theselected device. If the node data for the selected device is retrievedby the hand held RF controller 202 within a predetermined time outperiod in step 3106, then the controller permits a user to rename theselected device in step 3108. Alternatively, if the node data for theselected device is not retrieved by the hand held RF controller 202within a predetermined time out period in step 3106, then the controllercancels the renaming of the selected device in step 3110 and displays anerror message on the display 414 in step 3112.

Referring now to FIGS. 32 a-32 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and CONFIGURE 2004 i, using the menu-based program2000, the controller implements a method 3200 in which the controllerpermits a user to configure one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, within the system100. In particular, in step 3202 the hand held RF controller 202determines if a user has selected the configuring of a device within thesystem 100. If the user has selected the configuring of a device withinthe system 100, then the display 414 of the hand held RF controller 202prompts the user to select the device to be configured within the systemin step 3204.

Once a user of the hand held RF controller 202 has selected the devicethat will be configured, the node data for the selected device is thenretrieved by the controller. In an exemplary embodiment, the node datafor the selected device includes the node information frame 1702 for theselected device. If the node data for the selected device is retrievedby the hand held RF controller 202 within a predetermined time outperiod in step 3206, then the controller permits a user to configure theselected device in step 3208. In an exemplary embodiment, theconfiguration data 3208 a for the selected device includes: the valuefor the off delay for the selected device, the value for the panic ontime for the selected device, the value for panic enabled for theselected device, the power loss preset value for the selected device,and the power on state value for the selected device.

In an exemplary embodiment, the value for the off delay for the selecteddevice may, for example, be 1 second. In an exemplary embodiment, thevalue for the panic on time for the selected device may, for example, be1 second. In an exemplary embodiment, the value for panic enabled forthe selected device may, for example, be PANIC ENABLED. In an exemplaryembodiment, the power loss preset value for the selected device may, forexample, be the permissible tolerance in the power supply. In anexemplary embodiment, the power on state value for the selected devicemay, for example, be operational state of the device prior to the lossof power.

Alternatively, if the node data for the selected device is not retrievedby the hand held RF controller 202 within a predetermined time outperiod in step 3206, then the controller cancels the configuring of theselected device in step 3210 and displays an error message on thedisplay 414 in step 3212.

Referring now to FIGS. 33 a-33 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and VERSION 2004 j, using the menu-based program2000, the controller implements a method 3300 in which the controllerpermits a user to view the device version for one or more devices, suchas, for example, master and slave nodes, 102 and 104, respectively,within the system 100. In particular, in step 3302 the hand held RFcontroller 202 determines if a user has selected the viewing of theversion of a device within the system 100. If the user has selected theviewing of the version of a device within the system 100, then thedisplay 414 of the hand held RF controller 202 prompts the user toselect the device to be configured within the system in step 3304.

Once a user of the hand held RF controller 202 has selected the devicefor which the version will be viewed, the node data for the selecteddevice is then retrieved by the controller. In an exemplary embodiment,the node data for the selected device includes the node informationframe 1702 for the selected device. If the node data for the selecteddevice is retrieved by the hand held RF controller 202 within apredetermined time out period in step 3306, then the controller permitsa user to view the version information for the selected device in step3308. In an exemplary embodiment, the version information 3308 a for theselected device includes: the node ID value for the selected device, theapplication value for the selected device, the protocol value for theselected device, the library value for the selected device, themanufacturer value for the selected device, the product type value forthe selected device, and the product ID value for the selected device.

In an exemplary embodiment, the node ID value for the selected devicemay, for example, be a numeric value. In an exemplary embodiment, theapplication value for the selected device may, for example, be a numericdecimal value. In an exemplary embodiment, the protocol value for theselected device may, for example, be a numeric decimal value. In anexemplary embodiment, the library value for the selected device may, forexample, be a numeric decimal value. In an exemplary embodiment, themanufacturer value for the selected device may, for example, be analpha-numeric value. In an exemplary embodiment, the product type valuefor the selected device may, for example, be an alpha-numeric value. Inan exemplary embodiment, the product ID value for the selected devicemay, for example, be an alpha-numeric value.

Alternatively, if the node data for the selected device is not retrievedby the hand held RF controller 202 within a predetermined time outperiod in step 3306, then the controller cancels the viewing the versionof the selected device in step 3310 and displays an error message on thedisplay 414 in step 3312.

Referring now to FIGS. 34 a-34 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects DEVICES 2004 and ALL SWITCH 2004 k, using the menu-based program2000, the controller implements a method 3400 in which the controllerpermits a user to control the level of functionality for all switch forone or more devices, such as, for example, master and slave nodes, 102and 104, respectively, within the system 100. In particular, in step3402 the hand held RF controller 202 determines if a user has selectedthe controlling of the level of functionality for all switch of a devicewithin the system 100. If the user has selected the controlling of thelevel of functionality for all switch of a device within the system 100,then the display 414 of the hand held RF controller 202 prompts the userto select the device for which the level of functionality for all switchwill be configured within the system in step 3404.

Once a user of the hand held RF controller 202 has selected the devicefor which the level of functionality for all switch will be configured,the node data for the selected device is then retrieved by thecontroller. In an exemplary embodiment, the node data for the selecteddevice includes the node information frame 1702 for the selected device.If the node data for the selected device is retrieved by the hand heldRF controller 202 within a predetermined time out period in step 3406,then the controller determines if the selected device support all switchfunctionality in step 3408. If the hand held RF controller 202determines that the selected device supports all switch functionality,then the controller permits a user to configure the level offunctionality for all switch for the selected device in step 3310. In anexemplary embodiment, the level of all switch functionality 3310 a forthe selected device may be: not included, all on only, all off only, allon and off only.

In an exemplary embodiment, the node ID value for the selected devicemay, for example, be a numeric value. In an exemplary embodiment, theapplication value for the selected device may, for example, be a numericdecimal value. In an exemplary embodiment, the protocol value for theselected device may, for example, be a numeric decimal value. In anexemplary embodiment, the library value for the selected device may, forexample, be a numeric decimal value. In an exemplary embodiment, themanufacturer value for the selected device may, for example, be aalpha-numeric value. In an exemplary embodiment, the product type valuefor the selected device may, for example, be a alpha-numeric value. Inan exemplary embodiment, the product ID value for the selected devicemay, for example, be a alpha-numeric value.

Alternatively, if the node data for the selected device is not retrievedby the hand held RF controller 202 within a predetermined time outperiod in step 3406 or if the selected device does not support allswitch functionality in step 3408, then the controller cancels theconfiguring of the level of all switch functionality for the selecteddevice in step 3412 and displays an error message on the display 414 instep 3414.

Referring now to FIGS. 35 a-35 d, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SCENES 2006 and CREATE 2006 a, using the menu-based program2000, the controller implements a method 3500 in which the controllerpermits a user to create a scene using one or more devices, such as, forexample, master and slave nodes, 102 and 104, respectively, within thesystem 100. In particular, in step 3502 the hand held RF controller 202determines if a user has selected creating a scene within the system100. If the user has selected creating a scene within the system 100,then the display 414 of the hand held RF controller 202 prompts the userto enter the name of the scene to be created within the system in step3504.

Once a user of the hand held RF controller 202 has selected the name ofthe scene to be created in the system 100 in step 3504, the controllerthen waits for a user of the controller to select defining the scene tobe created in step 3506. Once a user of the hand held RF controller 202has selected defining the scene to be created in the system 100 in step3506, the controller then waits for a user of the controller to selectdevices for the scene to be created in step 3508.

If the hand held RF controller 202 determines that the selected devicefor the scene to be created are not controllable in step 3510, then thecontroller cancels the selection of the device for the scene to becreated and displays an error message on the display 414 in step 3512and then allows a user of the controller to continue selecting devicesfor the scene to be created in step 3508.

Alternatively, if the hand held RF controller 202 determines that theselected device for the scene to be created is controllable in step3510, then the controller enters the operational level for the deviceselected for the new scene in step 3514. The hand held RF controller 202then waits for a user of the hand held RF controller 202 to indicatewhether the selection of devices for the scene to be created in thesystem 100 has been completed in step 3516. If the selection of devicesfor the scene to be created in the system 100 is indicated by a user asnot completed in step 3516, then the hand held RF controller 202 waitsfor a user of the controller to select devices for the scene to becreated in step 3508.

In an exemplary embodiment, as illustrated in FIG. 35 c, the system 100includes the following scenes: BEDTIME, MORNING, MOVIETIME, MUSIC, FUNTIME, DINNER, and AWAY. In an exemplary embodiment, as illustrated inFIG. 35 d, the scene MORNING includes devices: LIVING ROOM LIGHT, HALLLIGHT, BEDROOM LIGHT, PORCH LIGHT, FRONT DOOR LIGHT, and KITCHEN LIGHThaving operational values of ON, OFF, 50%, OFF, ON, and OFF.

In an exemplary embodiment, during the operation of the method 3500, thesystem 100 may provide one or more predetermined names for scenes forselection by the user in order speed up the process of scene creation.

Referring now to FIG. 36, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SCENES 2006 and DELETE 2006 b, using the menu-based program2000, the controller implements a method 3600 in which the controllerpermits a user to delete a scene from the system 100. In particular, instep 3602 the hand held RF controller 202 determines if a user hasselected deleting a scene within the system 100. If the user hasselected deleting a scene within the system 100, then the display 414 ofthe hand held RF controller 202 prompts the user to enter the name ofthe scene to be deleted from the system in step 3604. Once a user of thehand held RF controller 202 has selected the name of the scene to bedeleted from the system 100 in step 3604, the controller then waits fora user of the controller to confirm the deletion of the scene in step3606.

Referring now to FIGS. 37 a-37 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SCENES 2006 and EDIT 2006 c, using the menu-based program 2000,the controller implements a method 3700 in which the controller permitsa user to edit a scene using one or more devices, such as, for example,master and slave nodes, 102 and 104, respectively, within the system100. In particular, in step 3702 the hand held RF controller 202determines if a user has selected editing a scene within the system 100.If a user has selected editing a scene within the system 100, then thedisplay 414 of the hand held RF controller 202 prompts the user to enterthe name of the scene to be edited within the system in step 3704.

Once a user of the hand held RF controller 202 has selected the name ofthe scene to be edited in the system 100 in step 3704, the controllerthen waits for a user of the controller to confirm the editing of thescene in step 3706. Once a user of the hand held RF controller 202 hasconfirmed editing of the scene in the system 100 in step 3706, thecontroller then waits for a user of the controller to select devices forthe scene to be edited in step 3708.

If the hand held RF controller 202 determines that the selected devicefor the scene to be edited are not controllable in step 3710, then thecontroller cancels the selection of the device for the scene to beedited and displays an error message on the display 414 in step 3712 andthen allows a user of the controller to continue selecting devices forthe scene to be created in step 3708.

Alternatively, if the hand held RF controller 202 determines that theselected device for the scene to be created is controllable in step3710, then the controller enters the operational level for the deviceselected for the scene to be edited in step 3714. The hand held RFcontroller 202 then waits for a user of the hand held RF controller 202to indicate whether the selection of devices for the scene to be editedin the system 100 has been completed in step 3716. If the selection ofdevices for the scene to be edited in the system 100 is indicated by auser as not completed in step 3716, then the hand held RF controller 202waits for a user of the controller to select devices for the scene to becreated in step 3708.

In an exemplary embodiment, during the operation of the method 3700, auser of the hand held RF controller 202 may edit one or more of thefollowing aspects of a selected scene: the name of the scene, the numberof the scene, the devices to be included in the scene, and theoperational states of the devices to be included in the scene.

Referring now to FIG. 38, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SCENES 2006 and ACTIVATE 2006 d, using the menu-based program2000, the controller implements a method 3800 in which the controllerpermits a user to activate a scene within the system 100. In particular,in step 3802 the hand held RF controller 202 determines if a user hasselected activating a scene within the system 100. If a user hasselected activating a scene within the system 100, then the display 414of the hand held RF controller 202 prompts the user to enter the name ofthe scene to be activated within the system in step 3804.

Once a user of the hand held RF controller 202 has selected the name ofthe scene to be activated in the system 100 in step 3804, the controllerthen waits for a user of the controller to confirm the activation of thescene in step 3806. Once a user of the hand held RF controller 202 hasconfirmed activating the scene in the system 100 in step 3806, thecontroller then activates the selected scene in the system 100. Once thehand held RF controller 202 determines that the selected scene has beenactivated in step 3808, the controller permits a user of the system 100to activate additional scenes in step 3802.

Referring now to FIG. 39, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SCENES 2006 and DEACTIVATE 2006 e, using the menu-based program2000, the controller implements a method 3900 in which the controllerpermits a user to deactivate a scene within the system 100. Inparticular, in step 3902 the hand held RF controller 202 determines if auser has selected deactivating a scene within the system 100. If a userhas selected deactivating a scene within the system 100, then thedisplay 414 of the hand held RF controller 202 prompts the user to enterthe name of the scene to be deactivated within the system in step 3904.

Once a user of the hand held RF controller 202 has selected the name ofthe scene to be deactivated in the system 100 in step 3804, thecontroller then waits for a user of the controller to confirm thedeactivation of the scene in step 3906. Once a user of the hand held RFcontroller 202 has confirmed deactivating the scene in the system 100 instep 3906, the controller then deactivates the selected scene in thesystem 100. Once the hand held RF controller 202 determines that theselected scene has been deactivated in step 3908, the controller permitsa user of the system 100 to deactivate additional scenes in step 3902.

Referring now to FIGS. 40 a-40 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects EVENTS 2008 and CREATE 2008 a, using the menu-based program2000, the controller implements a method 4000 in which the controllerpermits a user to create an event using one or more user defined sceneswithin the system 100. In particular, in step 4002 the hand held RFcontroller 202 determines if a user has selected creating an eventwithin the system 100. If the user has selected creating an event withinthe system 100, then the display 414 of the hand held RF controller 202prompts the user to enter the name of the event to be created within thesystem in step 4004.

Once a user of the hand held RF controller 202 has selected the name ofthe event to be created in the system 100 in step 4004, the controllerthen permits a user of the controller to enter the parameters 4006 a ofthe event in step 4006. In an exemplary embodiment, the parameters 4006a of the event include: the time of the event, the day of the event, thetype of event, the scene to be used in the event, and the activity levelof the event. If the event parameters have been completed in step 4008,then the hand held RF controller 202 permits a user to create furtherevents in step 4002.

Referring now to FIG. 41, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects EVENTS 2008 and DELETE 2008 b, using the menu-based program2000, the controller implements a method 4100 in which the controllerpermits a user to delete an event from the system 100. In particular, instep 4102 the hand held RF controller 202 determines if a user hasselected deleting an event from the system 100. If the user has selecteddeleting an event from the system 100, then the display 414 of the handheld RF controller 202 prompts the user to enter the name of the eventto be deleted from the system in step 4104. Once a user of the hand heldRF controller 202 has selected the name of the event to be deleted fromthe system 100 in step 4104, the controller then waits for a user of thecontroller to confirm the deletion of the event in step 4106.

Referring now to FIG. 42, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects EVENTS 2008 and EDIT 2008 c, using the menu-based program 2000,the controller implements a method 4200 in which the controller permitsa user to edit an event in the system 100. In particular, in step 4202the hand held RF controller 202 determines if a user has selectedediting an event in the system 100. If the user has selected editing anevent in the system 100, then the display 414 of the hand held RFcontroller 202 prompts the user to enter the name of the event to beedited in the system in step 4204. Once a user of the hand held RFcontroller 202 has selected the name of the event to be edited in thesystem 100 in step 4204, the controller then waits for a user of thecontroller to edit the parameters of the event in steps 4206 and 4208.

In an exemplary embodiment, during the operation of the method 4200, insteps 4206 and 4208, a user of the hand held RF controller 202 may editone or more of the following aspects of a selected event: the name ofthe event, the number of the event, the scenes to be included in thescene, the operational states of the scenes to be included in the event,and the timing of the event.

Referring now to FIG. 43, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects EVENTS 2008 and ACTIVATE 2008 d, using the menu-based program2000, the controller implements a method 4300 in which the controllerpermits a user to activate an event within the system 100. Inparticular, in step 4302 the hand held RF controller 202 determines if auser has selected activating an event within the system 100. If a userhas selected activating an event within the system 100, then the display414 of the hand held RF controller 202 prompts the user to enter thename of the event to be activated within the system in step 4304.

Once a user of the hand held RF controller 202 has selected the name ofthe event to be activated in the system 100 in step 4304, the controllerthen waits for a user of the controller to confirm the activation of theevent in step 4306. Once a user of the hand held RF controller 202 hasconfirmed activating the event in the system 100 in step 4306, thecontroller then activates the selected event in the system 100. Once thehand held RF controller 202 activates the selected event in step 4306,the controller permits a user of the system 100 to activate additionalevents in step 4302.

Referring now to FIG. 44, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects EVENTS 2008 and DEACTIVATE 2008 e, using the menu-based program2000, the controller implements a method 4400 in which the controllerpermits a user to deactivate an event within the system 100. Inparticular, in step 4402 the hand held RF controller 202 determines if auser has selected deactivating an event within the system 100. If a userhas selected deactivating an event within the system 100, then thedisplay 414 of the hand held RF controller 202 prompts the user to enterthe name of the event to be deactivated within the system in step 4404.

Once a user of the hand held RF controller 202 has selected the name ofthe event to be deactivated in the system 100 in step 4404, thecontroller then waits for a user of the controller to confirm thedeactivation of the event in step 4406. Once a user of the hand held RFcontroller 202 has confirmed deactivating the event in the system 100 instep 4406, the controller then deactivates the selected event in thesystem 100. Once the hand held RF controller 202 deactivates theselected event in step 4406, the controller permits a user of the system100 to deactivate additional events in step 4402.

Referring now to FIG. 45, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SYSTEM 2010 and DATE/TIME 2010 a, using the menu-based program2000, the controller implements a method 4500 in which the controllerpermits a user to select the date and time for the system 100. Inparticular, in step 4502 the hand held RF controller 202 determines if auser has selected entering the date and time for the system 100. If auser has selected entering the date and time for the system 100, thenthe display 414 of the hand held RF controller 202 prompts the user toenter the date and time for the system in step 4504. Once a user of thehand held RF controller 202 has entered and confirmed the date and timeof the system in step 4506, the controller then permits a user of thecontroller to enter another date and time for the system 100 in step4502.

Referring now to FIGS. 46 a-46 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SYSTEM 2010 and PANIC 2010 b, using the menu-based program 2000,the controller implements a method 4500 in which the controller permitsa user to configure the panic group 1202 for the system 100. Inparticular, in step 4602 the hand held RF controller 202 determines if auser has selected configuring the panic group 1202 for the system 100.If a user has selected configuring the panic group 1202 for the system100, then the display 414 of the hand held RF controller 202 prompts theuser to select a device such as, for example, a master or slave node,102 or 104, respectively, for inclusion in the panic group of the systemin step 4604. After a user of the hand held RF controller 202 hasselected a device for inclusion in the panic group 1202 of the system100 in step 4604, the controller then determines if the selected devicefor inclusion in the panic group of the system supports a panicoperation in step 4606.

If the hand held RF controller 202 determines that the device selectedfor inclusion in the panic group 1202 of the system 100 does not supporta panic operation in step 4606, then the controller displays an errormessage on the display 414 of the controller and cancels the selectionof the device in step 4608, and permits a user of the controller toselect another device in step 4604. Alternatively, if the hand held RFcontroller 202 determines that the device selected for inclusion in thepanic group 1202 of the system 100 does support a panic operation instep 4606, then the selected device is added to the panic group for thesystem in step 4610.

If a user of the hand held RF controller 202 indicates that more deviceswill be selected for inclusion in the panic group 1202 of the system 100in step 4612, then the controller permits a user of the controller toselect more devices for inclusion in the panic group for the system instep 4604.

Referring now to FIG. 47, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SYSTEM 2010 and LANGUAGE 2010 c, using the menu-based program2000, the controller implements a method 4700 in which the controllerpermits a user to select the language for the system 100. In particular,in step 4702 the hand held RF controller 202 determines if a user hasselected entering the language for the system 100. If a user hasselected entering the language for the system 100, then the display 414of the hand held RF controller 202 prompts the user to enter thelanguage for the system in step 4704. Once a user of the hand held RFcontroller 202 has entered and confirmed the language of the system instep 4706, the controller then permits a user of the controller to enteranother language for the system 100 in step 4702.

Referring now to FIGS. 48 a-48 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SYSTEM 2010 and VERSION 2010 d, using the menu-based program2000, the controller implements a method 4800 in which the controllerpermits a user to display the version 4800 a for the system 100. Inparticular, in step 4802 the hand held RF controller 202 determines if auser has selected displaying the version of the system 100. If a userhas selected viewing the version of the system 100, then the display 414of the hand held RF controller 202 displays the version 4800 a of thesystem in step 4804.

Referring now to FIGS. 49 a-49 c, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SYSTEM 2010 and REPLICATE 2010 e, using the menu-based program2000, the controller implements a method 4900 in which the controllerpermits a user to replicate the configuration of a system 100 containedwithin a first device, such as, for a example a first master node 102 ainto another device such as, for example, a second master node 102 b. Inparticular, in step 4902 the hand held RF controller 202 determines if auser has selected replicating the configuration of the system 100. If auser has selected replicating the configuration of the system 100, thenthe display 414 of the hand held RF controller 202 prompts a user of thecontroller to enter the name of the device to be replicated from in step4904 and the name of the device to be replicated to in step 4906.

After a user of the hand held RF controller 202 has entered the name ofthe device to be replicated from in step 4904 and the name of the deviceto be replicated to in step 4906, the node information for both of thedevices is transmitted to the controller. If the node information forboth of the devices is not received by the hand held RF controller 202within a predetermined timeout period in step 4908, then replication iscanceled in step 4910 and the display 414 of controller displays anerror message in step 4912.

Alternatively, if the node information for both of the devices isreceived by the hand held RF controller 202 within a predeterminedtimeout period in step 4908, then the display 414 of the controllerprompts a user of the controller to select the portions of theconfiguration of the system 100 to be replicated from the first masternode 102 a to the second master node 102 b in step 4914. After a user ofthe hand held RF controller 202 selects the portions of theconfiguration of the system 100 to be replicated from the first masternode 102 a to the second master node 102 b in step 4914, the replicationof the configuration of the system begins in step 4916.

If the replication of the configuration of the system 100 is notcompleted within a predetermined timeout period in step 4918, thenreplication is canceled in step 4920 and the display 414 of the handheld RF controller 202 displays an error message in step 4922.Alternatively, if the replication of the configuration of the system 100is completed within a predetermined timeout period in step 4918, thenthe hand held RF controller 202 prompts a user of the controller toindicate if additional replications are to be performed in step 4924. Ifa user of the hand held RF controller 202 indicates that additionalreplications of the configuration of the system 100 are to be performed,the controller then permits a user to select further replications instep 4902.

Referring now to FIGS. 50 a-50 c, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects SYSTEM 2010 and UPDATE 2010 f, using the menu-based program2000, the controller implements a method 5000 in which the controllerpermits a user to update one or more aspects of the configuration of asystem 100 in a device, such as, for a example a master node 102. Inparticular, in step 5002 the hand held RF controller 202 determines if auser has selected updating the configuration of the system 100 in adevice. If a user has selected updating the configuration of the system100 in a device, then the display 414 of the hand held RF controller 202prompts a user of the controller to enter the name of the device to beupdated in step 5004.

After a user of the hand held RF controller 202 has entered the name ofthe device to be updated in step 5004, the node information for thedevice is transmitted to the controller. If the node information for theselected device is not received by the hand held RF controller 202within a predetermined timeout period in step 5006, then the update iscanceled in step 5008 and the display 414 of controller displays anerror message in step 5010.

Alternatively, if the node information for both of the selected deviceis received by the hand held RF controller 202 within a predeterminedtimeout period in step 5006, then the display 414 of the controllerprompts a user of the controller to insert a firmware 5012 a containingthe system update into a firmware interface 5012 b in the deviceselected for updating in step 5012. After a user of the hand held RFcontroller 202 has inserted the firmware 5012 a containing the systemupdate into the firmware interface 5012 b in the device selected forupdating, the updating of the configuration of the system 100 in theselected device begins in step 5014.

If the updating of the configuration of the system 100 into the selecteddevice is not completed within a predetermined timeout period in step5016, then the update is canceled in step 5018 and the display 414 ofthe hand held RF controller 202 displays an error message in step 5020.Alternatively, if the update of the configuration of the system 100 inthe selected device is completed within a predetermined timeout periodin step 5016, then the hand held RF controller 202 prompts a user of thecontroller to indicate if additional updates are to be performed in step5022. If a user of the hand held RF controller 202 indicates thatadditional updates of the configuration of the system 100 are to beperformed, the controller then permits a user to select further updatesin step 5002.

Referring now to FIGS. 51 a-51 b, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects AWAY 2012 and EDIT 2012 a, using the menu-based program 2000,the controller implements a method 5100 in which the controller permitsa user to edit the away group 1402 of the system 100. In particular, instep 5102 the hand held RF controller 202 determines if a user hasselected editing the away group 1402 of the system 100. If a user hasselected editing the away group 1402 of the system 100, then a user ofthe hand held RF controller 202 may then edit the away group in step5104. If a user of the hand held RF controller 202 has not completedediting the away group 1402 of the system 100 in step 5106, the user maycontinue editing in step 5104.

Referring now to FIG. 52, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects AWAY 2012 and ACTIVATE 2012 b, using the menu-based program2000, the controller implements a method 5200 in which the controllerpermits a user to activate the away group 1402 of the system 100. Inparticular, in step 5202 the hand held RF controller 202 determines if auser has selected activating the away group 1402 of the system 100. If auser has selected activating the away group 1402 of the system 100, thenthe hand held RF controller 202 requests the user to confirm theactivation of the away group in step 5204. If a user of the hand held RFcontroller 202 confirms the activation of the away group 1402 of thesystem 100 in step 5204, then the controller randomly controls theoperation of the devices included in the away group in step 5206.

Referring now to FIG. 53, in an exemplary embodiment, during theoperation of the hand held RF controller 202, after a user sequentiallyselects AWAY 2012 and DEACTIVATE 2012 c, using the menu-based program2000, the controller implements a method 5300 in which the controllerpermits a user to deactivate the away group 1402 of the system 100. Inparticular, in step 5302 the hand held RF controller 202 determines if auser has selected deactivating the away group 1402 of the system 100. Ifa user has selected deactivating the away group 1402 of the system 100,then the hand held RF controller 202 requests the user to confirm thedeactivation of the away group in step 5304. If a user of the hand heldRF controller 202 confirms the deactivation of the away group 1402 ofthe system 100 in step 5304, then the controller resumes normal controlof the operation of the devices included in the away group in step 5306.

Referring now to FIG. 54, an exemplary embodiment of a table top RFcontroller 204 includes a controller 402 that is operably coupled to anRF transceiver 404, a memory 406, a network interface 408, a keypad 410,a user interface 412, a display 414, a battery 416, and a power adaptor5402. In an exemplary embodiment, the power adaptor 5402 is adapted tobe coupled to an external source of power and for adapting and couplingthe external source of power to the controller 402, the RF transceiver404, the memory 406, the network interface 408, the keypad 410, the userinterface 412, and the display 414.

In an exemplary embodiment, within the exception of the addition of thepower adaptor 5402, the design and operation of the table top RFcontroller 204 is substantially identical to the design and operation ofthe hand held RF controller 202.

In an exemplary embodiment, as illustrated in FIG. 54 a, the elements ofthe table top controller 204 may be positioned within and supported by ahousing 5404 having a cover 1922 that defines one or more openings forthe keypad 410, including one or more of the navigation buttons 1904,the OK button 1906, the BACK button 1908, the HOT buttons 1910, the ALLON button 1912 a, the ALL OFF button 1912 b, the PANIC button 1914, andthe MENU keys 1916, and the display 414.

Referring now to FIG. 55, an exemplary embodiment of a wall mount RFcontroller 206 includes a controller 402 that is operably coupled to anRF transceiver 404, a memory 406, a network interface 408, a keypad 410,a user interface 412, a display 414, a battery 416, and a power adaptor5402. In an exemplary embodiment, a power adaptor 5402 is adapted to becoupled to an external source of power and for adapting and coupling theexternal source of power to the controller 402, the RF transceiver 404,the memory 406, the network interface 408, the keypad 410, the userinterface 412, and the display 414.

In an exemplary embodiment, the design and operation of the wall mountRF controller 206 is substantially identical to the design and operationof the table top controller 204.

In an alternative embodiment, the operation of the wall mount RFcontroller 206 is limited to the control of scenes 802. In particular,in an alternative embodiment, the menu state engine 504 a of the wallmount RF controller 206 only includes a scene engine 602 b that onlyenables a main menu 2002 that permits a selection of scenes 2006.

In an exemplary embodiment, as illustrated in FIG. 55 a, the wall mountRF controller 206 may be positioned and mounted upon a surface 5502using a cover plate 5504 that defines an opening 5504 a for one or moreof the hot buttons 1910 and the display 414. In an exemplary embodiment,one or more of hot buttons 1910 permit a user of the wall mount RFcontroller 206 to select one or more corresponding scenes 802 forimplementation by the system 100. In an exemplary embodiment, the coverplate 5504 further defines one or more additional openings 5504 b formounting one or more corresponding other devices adjacent to the wallmount RF controller 206 such as, for example, the RF dimmer 310.

Referring now to FIG. 56, an exemplary embodiment of a USB RF controller208 includes a controller 402 that is operably coupled to an RFtransceiver 404, a memory 406, a network interface 408, a keypad 410, auser interface 412, a display 414, a battery 416, and a power adaptor5402. In an exemplary embodiment, a power adaptor 5402 is adapted to becoupled to an external source of power and for adapting and coupling theexternal source of power to the controller 402, the RF transceiver 404,the memory 406, the network interface 408, the keypad 410, the userinterface 412, and the display 414.

In an exemplary embodiment, the design and operation of the wall mountRF controller 206 is substantially identical to the design and operationof the table top controller 204.

In an alternative embodiment, the network interface 408 of the USB RFcontroller 208 enables a user of the USB RF controller to remotelycontrol and interface with the system 100 using a network interface suchas, for example, the Internet. In this manner, a user of the USB RFcontroller 208 may, for example, remotely configure the system from longdistances using a desktop, laptop, portable digital assistant, cellphone, or other suitable device capable of being operably coupled to theUSB RF controller.

Referring now to FIG. 57, an exemplary embodiment of an RF switch 302includes a controller 5702 that is operably coupled to: a memory 5704including a non-volatile memory 5706, an RF transceiver 5708, a lightswitch touch pad 5710, an install button 5712, an uninstall button 5714,an LED indicator light 5716, an associate button 5718, and a networkinterface 5720. In an exemplary embodiment, a conventional power supply5722 is operably coupled to the RF switch 302 for powering the operationof the RF switch, and the RF switch controllably couples and decouples aload 5724 to and from the power supply.

Referring to FIG. 57 a, in an exemplary embodiment, the RF switch 302includes a housing 5726, for containing and supporting the elements ofthe RF switch, and a cover 5728 that defines an opening 5828 a for thelight switch touch pad 5710 and an opening 5828 b for one or more otherbuttons 5730 that may, for example, include one or more of thefollowing: the install button 5712, the uninstall button 5714, and theassociate button 5718. In an exemplary embodiment, the RF switch 302further includes an external RF antenna 5732 that is operably coupled tothe RF transceiver 5708.

In an exemplary embodiment, the controller 5702 is adapted to monitorand control the operation of the memory 5704 including a non-volatilememory 5706, the RF transceiver 5708, the light switch touch pad 5710,the install button 5712, the install button 5714, the LED indicatorlight 5716, the associate button 5718, and the network interface 5720.In an exemplary embodiment, the controller 5702 includes one or more ofthe following: a conventional programmable general purpose controller,an application specific integrated circuit (ASIC), or other conventionalcontroller devices. In an exemplary embodiment, the controller 5702includes a model ZW0201 controller, commercially available from ZensysA/S.

Referring now to FIG. 58, in an exemplary embodiment, the controller5702 includes an operating system 5802, application programs 5804, and aboot loader 5806. In an exemplary embodiment, the operating system 502includes a serial communications driver 5802 a, a memory driver 5802 b,a display driver 5802 c, and a button input driver 5802 c. In anexemplary embodiment, the serial communications driver 5802 a controlsserial communications using the RF serial transceiver 5708, the memorydriver 5802 b controls the memory 5704 including the non volatile memory5706, the display driver 5802 c controls the LED indicator light 5716,and the button input driver 5802 d debounces button inputs provided by auser using one or more of: the light switch touchpad 5710, the installbutton 5712, the uninstall button 5714, and the associate button 5718.In an exemplary embodiment, the serial communications driver 5802 aincludes a Z-Wave™ serial API driver that implements a Z-Wave™ serialAPI protocol. The Z-Wave™ serial API driver that implements a Z-Wave™serial API protocol are both commercially available from Zensys A/S.

In an exemplary embodiment, the application programs 5804 include astate engine 5804 a. In an exemplary embodiment, the state engine 5804 apermits a user of one or more of the master nodes 102 to configure,control and monitor the operation of the RF switch 302.

Referring now to FIG. 59, in an exemplary embodiment, the state engine5804 a includes an installation engine 5902, a change of state engine5904, an association engine 5906, a child protection engine 5908, adelayed off engine 5910, a panic mode engine 5912, and a loss of powerdetection engine 5914.

In an exemplary embodiment, the installation engine 5902 monitors theoperating state of the RF Switch 302 and provides an indication to auser of the system 100 as to whether or not the switch has beeninstalled in the system. In this manner, the installation engine 5902facilitates the installation of the RF switch 302 into the system 100.

In an exemplary embodiment, the change of state engine 5904 monitors theoperating state of the RF switch 302 and, upon a change in operatingstate, transmits information to one or more of the master nodes 102regarding the configuration of the RF switch.

In an exemplary embodiment, the association engine 5906 is adapted tomonitor and control the operation of the RF switch 302 when the RFswitch is associated with one or more communication pathway 702.

In an exemplary embodiment, the child protection engine 5908 is adaptedto monitor and control the operation of the RF switch 302 when the RFswitch is operated in a child protection mode of operation.

In an exemplary embodiment, the delayed off engine 5910 is adapted tomonitor and control the operation of the RF switch 302 when the RFswitch is operated in a delayed off mode of operation.

In an exemplary embodiment, the panic mode engine 5912 is adapted tomonitor and control the operation of the RF switch 302 when the RFswitch is operated in a panic mode of operation.

In an exemplary embodiment, the loss of power detection engine 5914 isadapted to monitor the operating state of the RF switch 302 and, uponthe loss of power, save the operating state of the RF switch 302 intothe non volatile memory 5706. Upon the resumption of power to the RFswitch 302, the loss of power detection engine 5914 then retrieves thestored operating state of the RF switch 302 from the non volatile memory5706 and restores the operating state of the RF switch.

In an exemplary embodiment, the memory 5704, including the non volatilememory 5706, is operably coupled to and controlled by the controller5702. In an exemplary embodiment, as illustrated in FIG. 60, the memory5704, including the non volatile memory 5706, includes a copy of theoperating system 6002, a copy of the application programs 6004, a devicedatabase 6006, a scenes database 6008, an events database 6010, an awaydatabase 6012, and a system database 6014. In an exemplary embodiment,the memory 406 includes a model 24LC256 non volatile memory,commercially available from Microchip.

In an exemplary embodiment, the device database 6006 includesinformation that is specific to the RF switch 302. In an exemplaryembodiment, as illustrated in FIG. 61, the device database 6006 includesthe node information frame 1702 for the RF switch 302, an associationdatabase 6102 for the RF switch, a child protection database 6104 forthe RF switch, a delayed off database 6106 for the RF switch, a panicdatabase 6108 for the RF switch, and an operating state database 6110for the RF switch. In an exemplary embodiment, the association database6102 for the RF switch 302 includes information regarding thecommunication pathways 702 associated with the RF switch. In anexemplary embodiment, the child protection database 6104 for the RFswitch 302 includes information regarding the operating characteristicsof the RF switch when child protection is enabled. In an exemplaryembodiment, the delayed off database 6106 for the RF switch 302 includesinformation regarding the operating characteristics of the RF switchwhen delayed off is enabled. In an exemplary embodiment, the panicdatabase 6108 for the RF switch 302 includes information regarding theoperating characteristics of the RF switch when panic is enabled. In anexemplary embodiment, the operating state database 6110 for the RFswitch 302 includes information representative of the operating state ofthe RF switch.

In an exemplary embodiment, the device database 6006 includes one ormore of the following information: Default Parameter Offset Size ValueDescription Child 1 1 0 This is the child protection Protection mode forthe RF switch 302. Mode The default value of 0 corresponds to no childprotection. Off Delay 2 1 10 This is the number of seconds that the RFswitch 302 will flash the LED indicator 5716 before switching off theload 5724. Panic On 3 1 1 This is the number of seconds Time the load5724 will be on while in panic mode. Panic Off 4 1 1 This is the numberof seconds Time the load 5724 will be off while in panic mode. LoadState 5 1 0 This is the operational state of the load 5724. The defaultvalue is for the load to be OFF. All Switch 6 1 0xFF This indicates theState operational state of the RF switch 302 with regard to the allswitch group. The default is for the RF switch 302 to be included in theall switch group for both All ON and All OFF. Location 7 25 “LightedThis is the location name. Switch” There is a maximum of 24 charactersplus a null terminator. Load Boot 32 1 LAST This is the state the loadState VALUE 5724 takes upon booting up the RF switch 302. Panic Mode 331 Enabled This controls whether Panic Enable Mode is enabled ordisabled. Associated 34 5 0 The node IDs of nodes Nodes associated withthe RF switch 302.

In an exemplary embodiment, the scenes database 6008 includesinformation regarding the scenes 802 that include the RF switch 302. Inan exemplary embodiment, the events database 6010 includes informationregarding the events 1002 that include the RF switch 302. In anexemplary embodiment, the away database 6012 includes informationregarding the away group 1402 that includes the RF switch 302. In anexemplary embodiment, the system database 6014 includes systeminformation that includes the RF switch 302.

In an exemplary embodiment, the RF transceiver 5708 is operably coupledto and controlled and monitored by the controller 5702. In an exemplaryembodiment, the RF transceiver 5708 transmits and receives RFcommunications to and from other master and slave nodes, 102 and 104,respectively. In an exemplary embodiment, the RF transceiver 5708 may,for example, include one or more of the following: a conventional RFtransceiver, and/or the model ZW0201 RF transceiver commerciallyavailable from Zensys A/S.

In an exemplary embodiment, the light switch touch pad 5710 is aconventional light switch touch pad and is operably coupled to andcontrolled and monitored by the controller 5702. In an exemplaryembodiment, the light switch touch pad 5710 permits an operator of theRF switch 302, in combination with the system 100, to select the desiredmode of operation of the load 5724.

In an exemplary embodiment, the install button 5712 is operably coupledto and controlled and monitored by the controller 5702. In an exemplaryembodiment, the install button 5712 permits an operator of the RF switch302, in combination with the system 100, to install the RF switch intothe system.

In an exemplary embodiment, the uninstall button 5714 is operablycoupled to and controlled and monitored by the controller 5702. In anexemplary embodiment, the uninstall button 5714 permits an operator ofthe RF switch 302, in combination with the system 100, to uninstall theRF switch from the system.

In an exemplary embodiment, the LED indicator light 5716 is operablycoupled to and controlled and monitored by the controller 5702.

In an exemplary embodiment, the associate button 5718 is operablycoupled to and controlled and monitored by the controller 5702. In anexemplary embodiment, the associate button 5718 permits an operator ofthe RF switch 302, in combination with the system 100, to associate theRF switch with communication pathways 702 in the system.

Referring to FIG. 62, in an exemplary embodiment, during operation ofthe RF switch 302, the RF switch implements a method of installation6200 in which, if the RF switch has been operably coupled to the powersupply 5722, then the LED indicator lights 5716 are operated to indicatethis operational state in steps 6202 and 6204. Then, if the RF switch302 has been installed in the system 100, then the LED indicator lights5716 are operated to indicate this operational state in steps 6206 and6208. In an exemplary embodiment, the LED indicator lights 5716 flash onan off to indicate the operational state in steps 6202 and 6204, and theLED indicator lights 5716 are turned on to indicate the operationalstate in steps 6206 and 6208. In this manner, an operator of the system100 is provided with a visual and highly effective indication of theoperational state of the RF switch 302 that is local to the RF switch.This permits an installer of the RF switch 302, in a large house orcommercial building, with an effective means of determining theoperational state of the RF switch 302 that is both local to the RFswitch and avoids the need to interrogate a master node 102 to determinethe operational state.

Referring to FIG. 63, in an exemplary embodiment, during operation ofthe RF switch 302, the RF switch implements a method of detecting achange of state 6300 in which, if the operating state of the RF switchhas changed, then the node information frame 1702 for the RF switch istransmitted to one or more of the master nodes 102 of the system 100using the RF transceiver 5708 in steps 6302 and 6304.

Referring to FIGS. 64 a-64 b, in an exemplary embodiment, duringoperation of the RF switch 302, the RF switch implements a method ofassociation 6400 in which it is first determined if the RF switch isassociated with a plurality of slave nodes 104, e.g., slave nodes 104 aand 104 b, and thereby is associated with a plurality of communicationpathways, e.g., communication pathways 702 a and 702 b, in step 6402. Ifthe RF switch is associated with a plurality of slave nodes 104 andthereby is associated with a plurality of communication pathways 702,then a communication from the source node 706 that is principallydirected to, and directly affects, only one of the destination nodes 708a, is transmitted by multicasting the communication to all of the nodesassociated with the RF switch 302 in step 6404. I.e., the communicationis transmitted by the RF switch 302 through all of the communicationpathways, 702 a and 702 b, that the RF switch is associated with therebytransmitting the communication to the slave nodes, 104 a and 104 b, andthe destination nodes, 708 a and 708 b. The communication is thensingle-casted to only the nodes directly affected by the communicationin step 6406. I.e., the communication is only transmitted by the RFswitch 302 through the communication pathway 702 a thereby transmittingthe communication to the slave node 104 a and the destination node 708a. In this manner, the communication of the information to the affectednodes in the system 100 is assured by performing a multi-cast prior to asingle-cast.

Referring to FIG. 65, in an exemplary embodiment, during operation ofthe RF switch 302, the RF switch implements a method of child protection6500 in which it is first determined if the RF switch has active childprotection functionality in step 6502. If the RF switch 302 has activechild protection functionality, then it is then determined if the RFswitch has sequence control or remote control child protectionfunctionality in step 6504.

If the RF switch 302 has sequence control child protectionfunctionality, then, in order to permit local manual operation of theswitch, a user must depress the touchpad 5710 three times in step 6506.If a user of the RF switch 302 depresses the touchpad 5710 three timesin step 6506, then local manual operation of the RF switch, using thetouchpad 5710, is permitted in step 6508.

Alternatively, if the RF switch 302 has remote control child protectionfunctionality, then, local manual operation of the switch, using thetouchpad 5710, is not permitted. Consequently, if the RF switch 302 hasremote control child protection functionality, then local manualoperation of the switch, using the touchpad 5710, is not permitted instep 6510. As a result, control of the RF switch 302 is provided by oneor more of the master nodes 102 of the system 100.

Referring to FIGS. 66 a to 66 c, in an exemplary embodiment, duringoperation of the RF switch 302, the RF switch implements a method ofdelayed off 6600 in which it is first determined if the touchpad 5710 ofthe RF switch is in an on position in step 6602. If the touchpad 5710 ofthe RF switch 302 is in an on position, then it is then determined ifthe RF switch has remote control protection in step 6604. If the RFswitch 302 has remote control protection, then, local manual operationof the switch, using the touchpad 5710, is not permitted.

If the RF switch 302 does not have remote control protection, then it isthen determined if the RF switch has sequence control protection in step6606. If the RF switch 302 has sequence control protection, then, if auser of the RF switch depresses the touchpad 5710 of the RF switch threetimes in step 6608 or if the RF switch 302 does not have sequencecontrol protection, then it is determined if the touchpad was depressedfor at least some predefined minimum time period in step 6610.

If the touchpad 5710 of the RF switch 302 was depressed for at leastsome predefined minimum time, then it is determined if the touchpad wasalso subsequently depressed in step 6612. If the touchpad 5710 of the RFswitch 302 was also subsequently depressed, then the load 5724 that isoperably coupled to the RF switch is turned off in step 6614. If thetouchpad 5710 of the RF switch 302 was not also subsequently depressed,then it is determined if the RF switch 302 will be controlled by one ormore of the master nodes 102 in step 6616.

If the RF switch 302 will be controlled by one or more of the masternodes 102, then the operational state of the RF switch is controlled byone or more of the master nodes 102 in step 6618. Alternatively, if theRF switch 302 will not be controlled by one or more of the master nodes102, then the LED indicator light 5716 of the RF switch are flashed instep 6620. The RF switch 302 is then operated to turn off the load 5724operably coupled to the RF switch after a predetermined time period instep 6622, and then the LED indicator light 5716 of the RF switch areturned off in step 6624.

Referring to FIGS. 67 a to 67 b, in an exemplary embodiment, duringoperation of the RF switch 302, the RF switch implements a method ofpanic mode operation method 6700 in which it is first determined if apanic mode operation has been selected by a user of the system 100 instep 6702. In an exemplary embodiment, a panic mode operation may beselected by a user of the system 100 by operating one or more of themaster nodes 102 of the system.

If a panic mode operation has been selected by a user of the system 100,then the RF switch 302 is operated in accordance with the operatingparameters assigned to the RF switch during a panic mode of operationas, for example, contained within the panic database 6108, in step 6704.If the touchpad 5710 of the RF switch 302 is then depressed in step6706, then the RF switch is operated to decouple the load 5724 from thepower supply 5722 in step 6708. The panic mode of operation is thencanceled in step 6710.

Alternatively, if the touchpad 5710 of the RF switch 302 is not thendepressed in step 6706, then, if the panic mode of operation is canceledby a master node 102 of the system in step 6712, then the RF switch isoperated to decouple the load 5724 from the power supply 5722 in step6714. The panic mode of operation is then canceled in step 6716.

Alternatively, if the panic mode of operation is not canceled by amaster node 102 of the system in step 6712, then the RF switch 302 isoperated in accordance with the panic mode duty cycle settings for theRF switch contained within, for example, the panic database 6108, instep 6718. In an exemplary embodiment, the panic mode duty cyclesettings define an amount of time to couple the load 5724 to the powersupply 5722 and an amount of time to decouple the load from the powersupply. For example, if the load 5724 is a light, operation of the RFswitch 302 in a panic mode of operation will turn the light on and offin accordance with the panic mode duty cycle settings for the RF switch.If a panic mode of operation is canceled by a user of the system 100 instep 6720, then the operation of the RF switch 302 will return to normalin step 6722.

Referring to FIG. 68, in an exemplary embodiment, during operation ofthe RF switch 302, the RF switch implements a method of loss of powerdetection method 6700 in which it is first determined if a loss of powerhas occurred, for example, by monitoring the power supply 5722 in step6702. If a loss of power is detected in step 6802, then the currentoperational state of the RF switch 302 is stored in the RF switchoperational state database 6110 within the non-volatile memory 5704 ofthe RF switch in step 6804. It is then determined if power has beenrestored to the RF switch 302, for example, by monitoring the powersupply 5722 in step 6806. If power has been restored to the RF switch302, then the current operational state of the RF switch 302 isretrieved from the RF switch operational state database 6110 within thenon-volatile memory 5704, and the operational state of the RF switch isrestored to the operational state defined within the RF switchoperational state database 6110 in step 6808.

In an exemplary embodiment, the design, operation and functionality ofthe light switch touch pad 5710, the install button 5712, the uninstallbutton 5714, and the associate button 5718 may be combined into a singlepush button.

Referring now to FIG. 69, an exemplary embodiment of an RF receptacle304 includes a controller 6902 that is operably coupled to: a memory6904 including a non-volatile memory 6906, an RF transceiver 6908, anon/off switch 6910, an install button 6912, an uninstall button 6914, anLED indicator light 6916, an associate button 6918, a network interface6920, a conventional top plug receptacle 6922, and a conventional bottomplug receptacle 6924. In an exemplary embodiment, a conventional powersupply 6926 is operably coupled to the RF receptacle 304 for poweringthe operation of the RF receptacle, and the RF receptacle controllablycouples and decouples 1^(st) and 2^(nd) loads, 6928 and 6930,respectively, to and from the power supply.

Referring to FIG. 69 a, in an exemplary embodiment, the RF receptacle304 includes a housing 6932, for containing and supporting the elementsof the RF receptacle, and a cover 6934 that defines top and bottom plugopenings, 6934 a and 6934 b, for the top and bottom plug receptacles,6922 and 6924, respectively, an opening 6934 c for one or more buttons6936 that may, for example, include one or more of the following: theon/off switch 6910, the install button 6912, the uninstall button 6914,and the associate button 6918, and an opening 6934 d for the LEDindicator 6916. In an exemplary embodiment, the RF receptacle 304further includes an external RF antenna 6938 that is operably coupled tothe RF transceiver 6908.

In an exemplary embodiment, the controller 6902 is adapted to monitorand control the operation of the memory 6904, including a non-volatilememory 6906, the RF transceiver 6908, the on/off switch 6910, theinstall button 6912, the uninstall button 6914, the LED indicator light6916, the associate button 6918, the network interface 6920, the topplug receptacle 6922, and the bottom plug receptacle 6924. In anexemplary embodiment, the controller 6902 includes one or more of thefollowing: a conventional programmable general purpose controller, anapplication specific integrated circuit (ASIC), one or more conventionalrelays for controllably coupling or decoupling one or both of the plugreceptacles, 6922 and 6924, to or from the loads, 6928 and 6930,respectively, or other conventional controller devices. In an exemplaryembodiment, the controller 6902 includes a model ZW0201 controller,commercially available from Zensys A/S.

Referring now to FIG. 70, in an exemplary embodiment, the controller6902 includes an operating system 7002, application programs 7004, and aboot loader 7006. In an exemplary embodiment, the operating system 7002includes a serial communications driver 7002 a, a memory driver 7002 b,a display driver 7002 c, and a button input driver 7002 c. In anexemplary embodiment, the serial communications driver 7002 a controlsserial communications using the RF serial transceiver 6908, the memorydriver 7002 b controls the memory 6904, including the non volatilememory 6906, the display driver 7002 c controls the LED indicator light6916, and the button input driver 7002 d debounces button inputsprovided by a user using the on/off switch 6910, the install button6912, the uninstall button 6914, and the associate button 6918. In anexemplary embodiment, the serial communications driver 7002 a includes aZ-Wave™ serial API driver that implements a Z-Wave™ serial API protocol.The Z-Wave™ serial API driver that implements a Z-Wave™ serial APIprotocol are both commercially available from Zensys A/S.

In an exemplary embodiment, the application programs 7004 include astate engine 7004 a. In an exemplary embodiment, the state engine 7004 apermits a user of one or more of the master nodes 102 to configure,control and monitor the operation of the RF receptacle 304.

Referring now to FIG. 71, in an exemplary embodiment, the state engine7004 a includes an installation engine 7102, a change of state engine7104, an association engine 7106, a child protection engine 7108, adelayed off engine 7110, a panic mode engine 7112, and a loss of powerdetection engine 7114.

In an exemplary embodiment, the installation engine 7102 monitors theoperating state of the RF receptacle 304 and provides an indication to auser of the system 100 as to whether or not the RF receptacle has beeninstalled in the system. In this manner, the installation engine 5902facilitates the installation of the RF receptacle 304 into the system100.

In an exemplary embodiment, the change of state engine 7104 monitors theoperating state of the RF receptacle 304 and, upon a change in operatingstate, transmits information to one or more of the master nodes 102regarding the configuration of the RF receptacle.

In an exemplary embodiment, the association engine 7106 is adapted tomonitor and control the operation of the RF receptacle 304 when the RFreceptacle is associated with one or more communication pathway 702.

In an exemplary embodiment, the child protection engine 7108 is adaptedto monitor and control the operation of the RF receptacle 304 when theRF receptacle is operated in a child protection mode of operation.

In an exemplary embodiment, the delayed off engine 7110 is adapted tomonitor and control the operation of the RF receptacle 304 when the RFreceptacle is operated in a delayed off mode of operation.

In an exemplary embodiment, the panic mode engine 7112 is adapted tomonitor and control the operation of the RF receptacle 304 when the RFreceptacle is operated in a panic mode of operation.

In an exemplary embodiment, the loss of power detection engine 7114 isadapted to monitor the operating state of the RF receptacle 304 and,upon the loss of power, save the operating state of the RF receptacle304 into the non volatile memory 6906. Upon the resumption of power tothe RF receptacle 304, the loss of power detection engine 7114 thenretrieves the stored operating state of the RF receptacle 304 from thenon volatile memory 6906 and restores the operating state of the RFreceptacle.

In an exemplary embodiment, the memory 6904, including the non volatilememory 6906, is operably coupled to and controlled and monitored by thecontroller 6902. In an exemplary embodiment, as illustrated in FIG. 72,the memory 6904, including the non volatile memory 6906, includes a copyof the operating system 7202, a copy of the application programs 7204, adevice database 7206, a scenes database 7208, an events database 7210,an away database 7212, and a system database 7214. In an exemplaryembodiment, the memory 6904 includes a model 24 LC256 memory,commercially available from Microchip. In an exemplary embodiment, thenon volatile memory 6906 includes a model 24 LC256 memory, commerciallyavailable from Microchip.

In an exemplary embodiment, the device database 7206 includesinformation that is specific to the RF receptacle 304. In an exemplaryembodiment, as illustrated in FIG. 73, the device database 7206 includesthe node information frame 1702 for the RF receptacle 304, anassociation database 7302 for the RF receptacle, a child protectiondatabase 7304 for the RF receptacle, a delayed off database 7306 for theRF receptacle, a panic database 7308 for the RF receptacle, and anoperating state database 7310 for the RF receptacle 304. In an exemplaryembodiment, the association database 7302 for the RF receptacle 304includes information regarding the communication pathways 702 associatedwith the RF receptacle. In an exemplary embodiment, the child protectiondatabase 7304 for the RF receptacle 304 includes information regardingthe operating characteristics of the RF receptacle when child protectionis enabled. In an exemplary embodiment, the delayed off database 7306for the RF receptacle 304 includes information regarding the operatingcharacteristics of the RF receptacle when delayed off is enabled. In anexemplary embodiment, the panic database 7308 for the RF receptacle 304includes information regarding the operating characteristics of the RFreceptacle when panic is enabled. In an exemplary embodiment, theoperating state database 7310 for the RF receptacle 304 includesinformation representative of the operating state of the RF receptacle.

In an exemplary embodiment, the device database 7206 includes one ormore of the following information: Default Parameter Offset Size ValueDescription Child 1 1 0 This is the child protection Protection mode ofoperation for the RF Mode receptacle 304. Off Delay 2 1 10 This is thenumber of seconds that the RF receptacle 304 will flash the LEDindicator 6916 before switching off one or both of the loads, 6928and/or 6930. Panic On 3 1 1 This is the number of seconds Time theloads, 6928 and/or 6930, will be on while in panic mode. Panic Off 4 1 1This is the number of seconds Time the loads, 6928 and/or 6930, will beoff while in panic mode. Load State 5 1 0 This is the operational stateof the loads, 6928 and/or 6930. The default value is for the loads, 6928and/or 6930, to be OFF. All Switch 6 1 0xFF This is the state of theState loads, 6928 and/or 6930, inclusion in the all switch group. Thedefault is for the loads, 6928 and/or 6930, to be included for both AllON and All OFF. Location 7 25 Duplex This is the location name.Receptacle There is a maximum of 24 characters plus a null terminator.Load Boot 32 1 LAST This is the state the loads, State VALUE 6928 and/or6930, takes on booting up the RF receptacle 304. Panic Mode 33 1 EnabledThis controls whether Panic Enable Mode is enabled or disabled for theloads, 6928 and/or 6930.

In an exemplary embodiment, the scenes database 7208 includesinformation regarding the scenes 802 that include the RF receptacle 304.In an exemplary embodiment, the events database 7210 includesinformation regarding the events 1002 that include the RF receptacle304. In an exemplary embodiment, the away database 7212 includesinformation regarding the away group 1402 that includes the RFreceptacle 304. In an exemplary embodiment, the system database 7214includes system information that includes the RF receptacle 304.

In an exemplary embodiment, the RF transceiver 6908 is operably coupledto and controlled by the controller 6902. In an exemplary embodiment,the RF transceiver 6908 transmits and receives RF communications to andfrom other master and slave nodes, 102 and 104, respectively. In anexemplary embodiment, the RF transceiver 6908 may, for example, includeone or more of the following: a conventional RF transceiver, and/or themodel ZW0201 RF transceiver commercially available from Zensys A/S.

In an exemplary embodiment, the on/off switch 6910 is a conventionalon/off switch and is operably coupled to and controlled and monitored bythe controller 6902. In an exemplary embodiment, the on/off switch 6910permits an operator of the RF receptacle 304, in combination with thesystem 100, to select the desired mode of operation of the RF receptacle304.

In an exemplary embodiment, the install button 6912 is operably coupledto and controlled and monitored by the controller 6902. In an exemplaryembodiment, the install button 6912 permits an operator of the RFreceptacle 304, in combination with the system 100, to install the RFreceptacle into the system.

In an exemplary embodiment, the uninstall button 6914 is operablycoupled to and controlled and monitored by the controller 6902. In anexemplary embodiment, the uninstall button 6914 permits an operator ofthe RF receptacle 304, in combination with the system 100, to uninstallthe RF receptacle from the system.

In an exemplary embodiment, the LED indicator light 6916 is operablycoupled to and controlled and monitored by the controller 6902.

In an exemplary embodiment, the associate button 6918 is operablycoupled to and controlled and monitored by the controller 6902. In anexemplary embodiment, the associate button 6918 permits an operator ofthe RF receptacle 304, in combination with the system 100, to associatethe RF receptacle with communication pathways 702 in the system.

In an exemplary embodiment, the network interface 6920 is operablycoupled to and controlled and monitored by the controller 6902. In anexemplary embodiment, the network interface 6920 permits an operator ofthe RF receptacle 304, in combination with the system 100, to networkthe RF receptacle with one or more networks such as, for example, localarea networks, wide area networks, or the Internet.

In an exemplary embodiment, the top plug receptacle 6922 is coupled toand controlled by the controller 6902 and is adapted to receive aconventional male plug for operably coupling the top plug receptacle tothe 1^(st) load 6928. In an exemplary embodiment, the controller 6902controllably couples or decouples the top plug receptacle 6922 to orfrom the power supply 6926. In this manner, electrical power is providedto or denied to the 1^(st) load 6928.

In an exemplary embodiment, the bottom plug receptacle 6924 is coupledto and controlled by the controller 6902 and is adapted to receive aconventional male plug for operably coupling the bottom plug receptacleto the 2^(nd) load 6930. In an exemplary embodiment, the controller 6902controllably couples or decouples the bottom plug receptacle 6924 to orfrom the power supply 6926. In this manner, electrical power is providedto or denied to the 2^(nd) load 6930.

Referring to FIG. 74, in an exemplary embodiment, during operation ofthe RF receptacle 304, the RF receptacle implements a method ofinstallation 7400 in which, if the RF receptacle has been operablycoupled to the power supply 6926, then the LED indicator lights 6916 areoperated to indicate this operational state in steps 7402 and 7404.Then, if the RF receptacle 304 has been installed in the system 100,then the LED indicator lights 6916 are operated to indicate thisoperational state in steps 7406 and 7408. In an exemplary embodiment,the LED indicator lights 6916 flash on an off to indicate theoperational state in steps 7402 and 7404, and the LED indicator lightsare turned on to indicate the operational state in steps 7406 and 7408.In this manner, an operator of the system 100 is provided with a visualand highly effective indication of the operational state of the RFreceptacle 304 that is local to the RF receptacle. This permits aninstaller of the RF receptacle 304, in a large house or commercialbuilding, with an effective means of determining the operational stateof the RF receptacle 304 that is both local to the RF receptacle andavoids the need to interrogate a master node 102 to determine theoperational state.

Referring to FIG. 75, in an exemplary embodiment, during operation ofthe RF receptacle 304, the RF receptacle implements a method ofoperation 7500 in which, it is determined if a command has been receivedfrom a master node 102 to couple the power supply 6926 to one or moreboth of the plug receptacles, 6922 and 6944, in step 7502. If a commandhas been received from a master node 102 to couple the power supply 6926to one or more both of the plug receptacles, 6922 and 6944, then it isdetermined if the RF receptacle 304 includes a single plug receptacle ora pair of plug receptacles in step 7504. In an exemplary embodiment, forexample, the RF receptacle 304 may include: a) a pair of plug receptaclethat are both operably coupled to and controlled by the controller 6902;b) a pair of plug receptacles with only one of the plug receptaclesoperably coupled to and controlled by the controller and the other plugreceptacle directly coupled to the power supply 6926; or c) a singleplug receptacle that is operably coupled to and controlled by thecontroller.

If the RF receptacle 304 includes only a single plug receptacle that isoperably coupled to and controlled by the controller 6902, then thesingle plug receptacle is operably coupled to the power supply 6926 instep 7506. Alternatively, if the RF receptacle 304 includes only a pairof plug receptacles that are operably coupled to and controlled by thecontroller 6902, then both of the plug receptacles are operably coupledto the power supply 6926 in step 7508.

Referring to FIG. 76, in an exemplary embodiment, during operation ofthe RF receptacle 304, the RF receptacle implements a method ofdetecting a change of state 7600 in which, if the operating state of theRF receptacle has changed, then the node information frame 1702 for theRF receptacle is transmitted to one or more of the master nodes 102 ofthe system 100 using the RF transceiver 6908 in steps 7602 and 7604.

Referring to FIGS. 77 a-77 b, in an exemplary embodiment, duringoperation of the RF receptacle 304, the RF receptacle implements amethod of association 7700 in which it is first determined if the RFreceptacle is associated with a plurality of slave nodes 104, e.g.,slave nodes 104 a and 104 b, and thereby is associated with a pluralityof communication pathways, e.g., communication pathways 702 a and 702 b,in step 7702. If the RF receptacle 304 is associated with a plurality ofslave nodes 104 and thereby is associated with a plurality ofcommunication pathways 702, then a communication from the source node706 that is principally directed to, and directly affects, only one ofthe destination nodes 708 a, is transmitted by multicasting thecommunication to all of the nodes associated with the RF receptacle 304in step 7704. I.e., the communication is transmitted by the RFreceptacle 304 through all of the communication pathways, 702 a and 702b, that the RF receptacle is associated with thereby transmitting thecommunication to the slave nodes, 104 a and 104 b, and the destinationnodes, 708 a and 708 b. The communication is then single-casted to onlythe nodes directly affected by the communication in step 6406. I.e., thecommunication is only transmitted by the RF receptacle 304 through thecommunication pathway 702 a thereby transmitting the communication tothe slave node 104 a and the destination node 708 a. In this manner, thecommunication of the information to the affected nodes in the system 100is assured by performing a multi-cast prior to a single-cast.

Referring to FIG. 78, in an exemplary embodiment, during operation ofthe RF receptacle 304, the RF receptacle implements a method of childprotection 7800 in which it is first determined if the RF receptacle hasactive child protection functionality in step 7802. If the RF receptacle304 has active child protection functionality, then it is thendetermined if the RF receptacle has sequence control or remote controlchild protection functionality in step 7804.

If the RF receptacle 304 has sequence control child protectionfunctionality, then, in order to permit local manual operation of theswitch, a user must depress the on/off switch 6910 three times in step7806. If a user of the RF receptacle 304 depresses the on/off switch6910 three times in step 7806, then local manual operation of the RFreceptacle, using the on/off switch 6910, is permitted in step 7808.

Alternatively, if the RF receptacle 304 has remote control childprotection functionality, then, local manual operation of thereceptacle, using the on/off switch 6910, is not permitted.Consequently, if the RF receptacle 304 has remote control childprotection functionality, then local manual operation of the receptacle,using the on/off switch 6910, is not permitted in step 7810. As aresult, control of the RF receptacle 304 is provided by one or more ofthe master nodes 102 of the system 100.

Referring to FIGS. 79 a to 79 c, in an exemplary embodiment, duringoperation of the RF receptacle 304, the RF receptacle implements amethod of delayed off 7900 in which it is first determined if the on/offswitch 6910 of the RF receptacle is in an on position in step 7902. Ifthe on/off switch 6910 of the RF receptacle 304 is in an on position,then it is then determined if the RF receptacle has remote controlprotection in step 7904. If the RF receptacle 304 has remote controlprotection, then, local manual operation of the receptacle, using theon/off switch 6910, is not permitted.

If the RF receptacle 304 does not have remote control protection, thenit is then determined if the RF receptacle has sequence controlprotection in step 7906. If the RF receptacle 304 has sequence controlprotection, then, if a user of the RF receptacle depresses the on/offswitch 6910 of the RF receptacle three times in step 7908 or if the RFreceptacle 304 does not have sequence control protection, then it isdetermined if the on/off switch was depressed for at least somepredefined minimum time period in step 7910.

If the on/off switch 6910 of the RF receptacle 304 was depressed for atleast some predefined minimum time, then it is determined if the on/offswitch was also subsequently depressed in step 7912. If the on/offswitch 6910 of the RF receptacle 304 was also subsequently depressed,then one or both of the loads, 6928 and 6930, that are operably coupledto one or more both of the plug receptacles, 6922 and 6924, the RFreceptacle are decoupled from the power supply 6926 in step 7914. If theon/off switch 6910 of the RF receptacle 304 was not also subsequentlydepressed, then it is determined if the RF receptacle 304 will becontrolled by one or more of the master nodes 102 in step 7916.

If the RF receptacle 304 will be controlled by one or more of the masternodes 102, then the operational state of the RF receptacle is controlledby one or more of the master nodes 102 in step 7918. Alternatively, ifthe RF receptacle 304 will not be controlled by one or more of themaster nodes 102, then the LED indicator light 6916 of the RF receptacleare flashed in step 7920. The RF receptacle 304 is then operated to turnoff on or more of the loads, 6928 and 6930, operably coupled to the RFreceptacle after a predetermined time period in step 7922, and then theLED indicator light 6916 of the RF receptacle are turned off in step7924.

Referring to FIGS. 80 a to 80 b, in an exemplary embodiment, duringoperation of the RF receptacle 304, the RF receptacle implements amethod of panic mode operation method 8000 in which it is firstdetermined if a panic mode operation has been selected by a user of thesystem 100 in step 8002. In an exemplary embodiment, a panic modeoperation may be selected by a user of the system 100 by operating oneor more of the master nodes 102 of the system.

If a panic mode operation has been selected by a user of the system 100,then the RF receptacle 304 is operated in accordance with the operatingparameters assigned to the RF receptacle during a panic mode ofoperation as, for example, contained within the panic database 7308, instep 8004. If the on/off switch 6910 of the RF receptacle 304 is thendepressed in step 8006, then the RF receptacle is operated to decoupleone or both of the loads, 6928 and 6930, from the power supply 6926 instep 8008. The panic mode of operation is then canceled in step 8010.

Alternatively, if the on/off switch 6910 of the RF receptacle 304 is notthen depressed in step 8006, then, if the panic mode of operation iscanceled by a master node 102 of the system in step 8012, then the RFreceptacle is operated to decouple one or both of the loads, 6928 and6930, from the power supply 6926 in step 8014. The panic mode ofoperation is then canceled in step 8016.

Alternatively, if the panic mode of operation is not canceled by amaster node 102 of the system in step 8012, then the RF receptacle 304is operated in accordance with the panic mode duty cycle settings forthe RF receptacle contained within, for example, the panic database7308, in step 8018. In an exemplary embodiment, the panic mode dutycycle settings define an amount of time to couple one or both of theloads, 6928 and 6930, to the power supply 6926 and an amount of time todecouple one or both of the loads from the power supply. For example, ifthe load 6928 is a light, operation of the RF receptacle 304 in a panicmode of operation will turn the light on and off in accordance with thepanic mode duty cycle settings for the RF receptacle. If a panic mode ofoperation is canceled by a user of the system 100 in step 8020, then theoperation of the RF receptacle 304 will return to normal in step 8022.

Referring to FIG. 81, in an exemplary embodiment, during operation ofthe RF receptacle 304, the RF receptacle implements a method of loss ofpower detection method 8100 in which it is first determined if a loss ofpower has occurred, for example, by monitoring the power supply 6926 instep 8102. If a loss of power is detected in step 8102, then the currentoperational state of the RF receptacle 304 is stored in the RFreceptacle operational state database 7310 within the non-volatilememory 6906 of the RF receptacle in step 8104. It is then determined ifpower has been restored to the RF receptacle 304, for example, bymonitoring the power supply 6926 in step 8106. If power has beenrestored to the RF receptacle 304, then the current operational state ofthe RF receptacle 304 is retrieved from the RF receptacle operationalstate database 7310 within the non-volatile memory 6906, and theoperational state of the RF receptacle is restored to the operationalstate defined within the RF receptacle operational state database 7310in step 8108.

In an exemplary embodiment, the design, operation and functionality ofthe on/off switch 6910, the install button 6912, the uninstall button6914, and the associate button 6918 may be combined into a single pushbutton.

Referring now to FIG. 82, an exemplary embodiment of an RF smart dimmer306 includes a controller 8202 that is operably coupled to: a memory8204, including a non-volatile memory 8206, an RF transceiver 8208, alight switch touch pad 8210, an install button 8212, an uninstall button8214, an LED indicator light 8216, an associate button 8218, a networkinterface 8220, a brighten button 8222, a dimmer button 8224, a manualdimmer preset button 8226, and a loss of power detector 8228. In anexemplary embodiment, a conventional power supply 8230 is operablycoupled to the RF smart dimmer 306 for powering the operation of the RFsmart dimmer, and the RF smart dimmer controllably couples and decouplesa load 8232 to and from the power supply.

In an exemplary embodiment, the controller 8202 is adapted to monitorand control the operation of the memory 8204, including a non-volatilememory 8206, the RF transceiver 8208, the light switch touch pad 8210,the install button 8212, the uninstall button 8214, the LED indicatorlight 8216, the associate button 8218, the network interface 8220, thebrighten button 8222, the dimmer button 8224, the manual dimmer presetbutton 8226, and the loss of power detector 8228. In an exemplaryembodiment, the controller 8202 includes one or more of the following: aconventional programmable general purpose controller, an applicationspecific integrated circuit (ASIC), or other conventional controllerdevices. In an exemplary embodiment, the controller 8202 includes amodel ZW0201 controller, commercially available from Zensys A/S.

Referring now to FIG. 83, in an exemplary embodiment, the controller8202 includes an operating system 8302, application programs 8304, and aboot loader 8306. In an exemplary embodiment, the operating system 8302includes a serial communications driver 8302 a, a memory driver 8302 b,a display driver 8302 c, and a button input driver 8302 d. In anexemplary embodiment, the serial communications driver 8302 a controlsserial communications using the RF serial transceiver 8208, the memorydriver 8302 b controls the memory 8204, including the non volatilememory 8206, the display driver 8302 c controls the LED indicator light8216, and the button input driver 8302 d debounces button inputsprovided by a user using one or more of: the light switch touchpad 8210,the install button 8212, the uninstall button 8214, the associate button8218, the brighten button 8222, the dimmer button 8224, and the manualdimmer preset button 8226. In an exemplary embodiment, the serialcommunications driver 8302 a includes a Z-Wave™ serial API driver thatimplements a Z-Wave™ serial API protocol. The Z-Wave™ serial API driverthat implements a Z-Wave™ serial API protocol are both commerciallyavailable from Zensys A/S.

In an exemplary embodiment, the application programs 8304 include astate engine 8304 a. In an exemplary embodiment, the state engine 8304 apermits a user of one or more of the master nodes 102 to configure,control and monitor the operation of the RF smart dimmer 306.

Referring now to FIG. 84, in an exemplary embodiment, the state engine8304 a includes an installation engine 8402, a change of state engine8404, an association engine 8406, a child protection engine 8408, adelayed off engine 8410, a panic mode engine 8412, and a loss of powerdetection engine 8414.

In an exemplary embodiment, the installation engine 8402 monitors theoperating state of the RF smart dimmer 306 and provides an indication toa user of the system 100 as to whether or not the RF smart dimmer hasbeen installed in the system. In this manner, the installation engine8402 facilitates the installation of the RF smart dimmer 306 into thesystem 100.

In an exemplary embodiment, the change of state engine 8404 monitors theoperating state of the RF smart dimmer 306 and, upon a change inoperating state, transmits information to one or more of the masternodes 102 regarding the configuration of the RF smart dimmer.

In an exemplary embodiment, the association engine 8406 is adapted tomonitor and control the operation of the RF smart dimmer 306 when the RFsmart dimmer is associated with one or more communication pathway 702.

In an exemplary embodiment, the child protection engine 8408 is adaptedto monitor and control the operation of the RF smart dimmer 306 when theRF smart dimmer is operated in a child protection mode of operation.

In an exemplary embodiment, the delayed off engine 8410 is adapted tomonitor and control the operation of the RF smart dimmer 306 when the RFsmart dimmer is operated in a delayed off mode of operation.

In an exemplary embodiment, the panic mode engine 8412 is adapted tomonitor and control the operation of the RF smart dimmer 306 when the RFsmart dimmer is operated in a panic mode of operation.

In an exemplary embodiment, the loss of power detection engine 8414 isadapted to monitor the operating state of the RF smart dimmer 306 and,upon the loss of power, save the operating state of the RF smart dimmerinto the non volatile memory 8206. Upon the resumption of power to theRF smart dimmer 306, the loss of power detection engine 8414 thenretrieves the stored operating state of the RF smart dimmer 306 from thenon volatile memory 8206 and restores the operating state of the RFsmart dimmer.

In an exemplary embodiment, the memory 8204, including the non volatilememory 8206, is operably coupled to and controlled by the controller8202. In an exemplary embodiment, as illustrated in FIG. 85, the memory8204, including the non volatile memory 8206, includes a copy of theoperating system 8502, a copy of the application programs 8504, a devicedatabase 8506, a scenes database 8508, an events database 8510, an awaydatabase 8512, and a system database 8514. In an exemplary embodiment,the memory 8204 includes a model 24LC256 non volatile memory,commercially available from Microchip.

In an exemplary embodiment, the device database 8506 includesinformation that is specific to the RF smart dimmer 306. In an exemplaryembodiment, as illustrated in FIG. 86, the device database 7206 includesthe node information frame 1702 for the RF smart dimmer 306, a presetdatabase 7302 for the RF smart dimmer, a delayed off database 7304 forthe RF smart dimmer, an association database 7306 for the RF smartdimmer, a child protection database 7308 for the RF smart dimmer, apanic database 7310 for the RF smart dimmer, and an operating statedatabase 7312 for the RF smart dimmer. In an exemplary embodiment, thepreset database 7302 includes information regarding the preset levels ofthe RF smart dimmer 306. In an exemplary embodiment, the delayed offdatabase 7304 for the RF smart dimmer 306 includes information regardingthe operating characteristics of the RF smart dimmer when delayed off isenabled. In an exemplary embodiment, the association database 7306 forthe RF smart dimmer 306 includes information regarding the communicationpathways 702 associated with the RF smart dimmer. In an exemplaryembodiment, the child protection database 7308 for the RF smart dimmer306 includes information regarding the operating characteristics of theRF smart dimmer when child protection is enabled. In an exemplaryembodiment, the panic database 7310 for the RF smart dimmer 306 includesinformation regarding the operating characteristics of the RF smartdimmer when panic is enabled. In an exemplary embodiment, the operatingstate database 7312 for the RF smart dimmer 306 includes informationrepresentative of the operating state of the RF smart dimmer.

In an exemplary embodiment, the device database 8506 includes one ormore of the following information: Default Parameter Offset Size ValueDescription Child 1 1 0 This is the level of child Protection protectionfor the RF smart Mode dimmer 306. The default value of 0 corresponds tono child protection for the RF smart dimmer. Off Delay 2 1 10 This isthe number of seconds that the RF smart dimmer 306 will flash the LEDindicator 8216 before switching off the load 8232. Panic On 3 1 1 Thisis the number of seconds Time the load 8232 will be on while in panicmode. Panic Off 4 1 1 This is the number of seconds Time the load 8232will be off while in panic mode. Load Level 5 1 0 This is the state ofthe load 8232. The default value is for the load 8232 to be OFF. AllSwitch 6 1 0 This is the operational State status of the RF smart dimmer306 with regard to inclusion in the all switch group. The default is forthe RF smart dimmer 306 to be excluded from both all ON and all OFF.Location 7 25 “Smart This is the location name. Dimmer” There is amaximum of 24 characters plus a null terminator. Power Loss 32 1 6 Thisis the number of zero Preset crossings not detected that will triggerthe operational state of the load 8232 level to be saved to non volatilememory 8206. Level Boot 33 1 LAST This is the operational state StateVALUE the load 8232 takes on boot. Panic Mode 34 1 Enabled This controlswhether Panic Enable Mode is enabled or disabled. Associated 35 5 0 Thenode IDs of associated Nodes nodes. Preset 40 1 4 The preset level ofthe Level load 8232. Ramp Time 41 1 3 The number of seconds to ramp theload 8232 from 0% to 100%.

In an exemplary embodiment, the scenes database 8508 includesinformation regarding the scenes 802 that include the RF smart dimmer306. In an exemplary embodiment, the events database 8510 includesinformation regarding the events 1002 that include the RF smart dimmer306. In an exemplary embodiment, the away database 8512 includesinformation regarding the away group 1402 that includes the RF smartdimmer 306. In an exemplary embodiment, the system database 8514includes system information that includes the RF smart dimmer 306.

In an exemplary embodiment, the RF transceiver 8208 is operably coupledto and controlled and monitored by the controller 8202. In an exemplaryembodiment, the RF transceiver 8208 transmits and receives RFcommunications to and from other master and slave nodes, 102 and 104,respectively. In an exemplary embodiment, the RF transceiver 8208 may,for example, include one or more of the following: a conventional RFtransceiver, and/or the model ZW0201 RF transceiver commerciallyavailable from Zensys A/S.

In an exemplary embodiment, the light switch touch pad 8210 is aconventional light switch touch pad and is operably coupled to andcontrolled and monitored by the controller 8202. In an exemplaryembodiment, the light switch touch pad 8210 permits an operator of theRF switch 302, in combination with the system 100, to select the desiredmode of operation of the load 8232.

In an exemplary embodiment, the install button 8212 is operably coupledto and controlled and monitored by the controller 8202. In an exemplaryembodiment, the install button 8212 permits an operator of the RF smartdimmer 306, in combination with the system 100, to install the RF smartdimmer into the system.

In an exemplary embodiment, the uninstall button 8214 is operablycoupled to and controlled and monitored by the controller 8202. In anexemplary embodiment, the uninstall button 8214 permits an operator ofthe RF smart dimmer 306, in combination with the system 100, touninstall the RF smart dimmer from the system.

In an exemplary embodiment, the LED indicator light 8216 is operablycoupled to and controlled and monitored by the controller 8202.

In an exemplary embodiment, the associate button 8218 is operablycoupled to and controlled and monitored by the controller 8202. In anexemplary embodiment, the associate button 8218 permits an operator ofthe RF smart dimmer 306, in combination with the system 100, toassociate the RF smart dimmer with communication pathways 702 in thesystem.

In an exemplary embodiment, the network interface 8220 is operablycoupled to and controlled and monitored by the controller 8202. In anexemplary embodiment, the network interface 8220 permits RF smart dimmer306, in combination with the system 100, to be networked with otherdevice within and outside of the system.

In an exemplary embodiment, the brighten button 8222 is operably coupledto and controlled and monitored by the controller 8202. In an exemplaryembodiment, the brighten button 8222 permits an operator of the RF smartdimmer 306, in combination with the system 100, to increase the level ofcurrent provided by the power supply 8230 to the load 8232.

In an exemplary embodiment, the dimming button 8224 is operably coupledto and controlled and monitored by the controller 8202. In an exemplaryembodiment, the dimming button 8224 permits an operator of the RF smartdimmer 306, in combination with the system 100, to decrease the level ofcurrent provided by the power supply 8230 to the load 8232.

In an exemplary embodiment, the manual dimmer preset button 8226 isoperably coupled to and controlled and monitored by the controller 8202.In an exemplary embodiment, the manual dimmer preset button 8226 permitsan operator of the RF smart dimmer 306, in combination with the system100, to select one or more preset levels of current provided by thepower supply 8230 to the load 8232.

In an exemplary embodiment, the loss of power detector 8228 is operablycoupled to and controlled and monitored by the controller 8202. In anexemplary embodiment, the loss of power detector 8228 permits anoperator of the RF smart dimmer 306, in combination with the system 100,to detect a loss of electrical power from the power supply 8230.

Referring to FIG. 87, in an exemplary embodiment, during operation ofthe RF smart dimmer 306, the RF smart dimmer implements a method ofinstallation 8700 in which, if the RF smart dimmer has been operablycoupled to the power supply 8230, then the LED indicator lights 8216 areoperated to indicate this operational state in steps 8702 and 8704.Then, if the RF smart dimmer 306 has been installed in the system 100,then the LED indicator lights 8216 are operated to indicate thisoperational state in steps 8706 and 8708. In an exemplary embodiment,the LED indicator lights 8216 flash on an off to indicate theoperational state in steps 8702 and 8704, and the LED indicator lights8216 are turned on to indicate the operational state in steps 8706 and8708. In this manner, an operator of the system 100 is provided with avisual and highly effective indication of the operational state of theRF smart dimmer 306 that is local to the RF smart dimmer. This permitsan installer of the RF smart dimmer 306, in a large house or commercialbuilding, with an effective means of determining the operational stateof the RF smart dimmer 306 that is both local to the RF smart dimmer andavoids the need to interrogate a master node 102 to determine theoperational state.

Referring to FIG. 88, in an exemplary embodiment, during operation ofthe RF smart dimmer 306, the RF smart dimmer implements a method ofoperation 8800 in which it is determined if the on/off switch 8210 ofthe RF smart dimmer has been depressed in step 8802. If the on/offswitch 8210 of the RF smart dimmer 306 has been depressed, then it isdetermined if the RF smart dimmer has been installed in the system 100in step 8804. If the RF smart dimmer 306 has been installed in thesystem 100, then the node information frame 1702 for the RF smart dimmeris transmitted to one or more of the master nodes 102 of the system 100using the RF transceiver 8208 in step 8806.

Alternatively, if the RF smart dimmer 306 has not been installed in thesystem 100, or after the node information frame 1702 for the RF smartdimmer is transmitted to one or more of the master nodes 102 of thesystem 100, it is determined if the on/off switch 8210 of the RF smartdimmer has been released in step 8808. If the on/off switch 8210 of theRF smart dimmer 306 has been released, then the RF smart dimmer operablygradually couples the power supply 8230 to the load 8232 in accordancewith the preset levels in step 8810. For example, if the load 8232 is alight, in step 8810, the RF smart dimmer 306 gradually increases thelighting level of the light to the preset level.

Referring to FIGS. 89 a and 89 b, in an exemplary embodiment, duringoperation of the RF smart dimmer 306, the RF smart dimmer implements amethod of operation 8900 in which it is determined if the RF smartdimmer 306 is operably coupling the power supply 8230 to the load 8232in step 8902. For example, if the load 8232 is a light, in step 8902, itis determined if the light is on. If the RF smart dimmer 306 is operablycoupling the power supply 8230 to the load 8232, then it is determinedif a user of the smart dimmer 306 has depressed the brighten or dimmingbuttons, 8222 or 8224, respectively, in step 8904. If a user of the RFsmart dimmer 306 has depressed the brighten or dimming buttons, 8222 or8224, respectively, then the RF smart dimmer increases or decreases thepreset level of current supplied to the load 8232 by the power supply8203 in step 8906. For example, in step 8906, if the load 8232 is alight, then, if the brighten button 8222 was depressed, the presetlighting level is increased. Alternatively, for example, in step 8906,if the load 8232 is a light, then, if the dimming button 8224 wasdepressed, the preset lighting level is decreased.

Alternatively, if the RF smart dimmer 306 is not operably coupling thepower supply 8230 to the load 8232, then it is determined if a user ofthe smart dimmer 306 has depressed the brighten or dimming buttons, 8222or 8224, respectively, in steps 8908 and 8910. If a user of the RF smartdimmer 306 has depressed the brighten or dimming buttons, 8222 or 8224,respectively, then the RF smart dimmer increases or decreases the presetlevel of current supplied to the load 8232 by the power supply 8203 tothe maximum levels in step 8912. For example, in step 8912, if the load8232 is a light, then, if the brighten button 8222 was depressed, thepreset lighting level is increased to maximum possible level.Alternatively, for example, in step 8912, if the load 8232 is a light,then, if the dimming button 8224 was depressed, the preset lightinglevel is decreased to the minimum possible level.

Referring to FIGS. 90 a and 90 b, in an exemplary embodiment, duringoperation of the RF smart dimmer 306, the RF smart dimmer implements amethod of operation 9000 in which it is determined if the RF smartdimmer 306 is operably coupling the power supply 8230 to the load 8232in step 9002. For example, if the load 8232 is a light, in step 8902, itis determined if the light is on. If the RF smart dimmer 306 is operablycoupling the power supply 8230 to the load 8232, then it is determinedif the preset levels for the RF smart dimmer were set by one or more ofthe master nodes 102 in step 9004. If the preset levels for the RF smartdimmer 306 were set by one or more of the master nodes 102, then levelof current supplied by the power supply 8230 to the load 8232 is set tothe preset level defined by the master nodes 102 in step 9006. Forexample, if the load 8232 is a light, then, in step 9006, the lightinglevel of the light is set to the preset lighting levels defined by themaster nodes 102.

Alternatively, if the RF smart dimmer 306 is not operably coupling thepower supply 8230 to the load 8232, then it is determined if any of themaster nodes 102 have directed the RF smart dimmer to operably couplethe power supply 8230 to the load 8232 in step 9008. If any of themaster nodes 102 have directed the RF smart dimmer 306 to operablycouple the power supply 8230 to the load 8232, then the RF smart dimmercouples the power supply 8230 to the load 8232 using the preset currentlevels contained within the preset database 7302 of the device database7206 of the non volatile memory 8206 of the RF smart dimmer in step9010.

Referring to FIG. 91, in an exemplary embodiment, during operation ofthe RF smart dimmer 306, the RF smart dimmer implements a method ofoperation 9100 in which it is determined if the RF smart dimmer 306 isoperably coupling the power supply 8230 to the load 8232 in step 9102.For example, if the load 8232 is a light, in step 9102, it is determinedif the light is on. If the RF smart dimmer 306 is not operably couplingthe power supply 8230 to the load 8232, then it is determined if theon/off switch 8210 of the RF smart dimmer has been depressed for atleast some preset time in step 9104. If the on/off switch 8210 of the RFsmart dimmer 306 has been depressed for at least some preset time, thenRF smart dimmer is operated to supply the maximum level of current fromthe power supply 8230 to the load 8232 in step 9106. For example, if theload 8232 is a light, then, in step 9106, the lighting level of thelight is set to the maximum possible level.

Referring to FIGS. 92 a to 92 c, in an exemplary embodiment, duringoperation of the RF smart dimmer 306, the RF smart dimmer implements amethod of delayed off 9200 in which it is first determined if thetouchpad 8210 of the RF smart dimmer is in an on position in step 9202.If the touchpad 8210 of the RF smart dimmer 306 is in an on position,then it is then determined if the RF smart dimmer has remote controlprotection in step 9204. If the RF smart dimmer 306 has remote controlprotection, then, local manual operation of the RF smart dimmer is notpermitted.

If the RF smart dimmer 306 does not have remote control protection, thenit is then determined if the RF smart dimmer has sequence controlprotection in step 9206. If the RF smart dimmer 306 has sequence controlprotection, then, if a user of the RF smart dimmer depresses thetouchpad 8210 of the RF smart dimmer three times in step 9208 or if theRF smart dimmer does not have sequence control protection, then it isdetermined if the touchpad was depressed for at least some predefinedminimum time period in step 9210.

If the touchpad 8210 of the RF smart dimmer 306 was depressed for atleast some predefined minimum time, then it is determined if thetouchpad was also subsequently depressed in step 9212. If the touchpad8210 of the RF smart dimmer 306 was also subsequently depressed, thenthe load 8232 that is operably coupled to the RF smart dimmer 306 isturned off in step 9214. If the touchpad 8210 of the RF smart dimmer 306was not also subsequently depressed, then it is determined if the RFsmart dimmer 306 will be controlled by one or more of the master nodes102 in step 9216.

If the RF smart dimmer 306 will be controlled by one or more of themaster nodes 102, then the operational state of the RF smart dimmer iscontrolled by one or more of the master nodes 102 in step 9218.Alternatively, if the RF smart dimmer 306 will not be controlled by oneor more of the master nodes 102, then the LED indicator light 8216 ofthe RF smart dimmer are flashed in step 9220. The RF smart dimmer 306 isthen operated to turn off the load 8232 operably coupled to the RF smartdimmer after a predetermined time period in step 9222, and then the LEDindicator light 8216 of the RF smart dimmer are turned off in step 9224.

Referring to FIGS. 93 a-93 b, in an exemplary embodiment, duringoperation of the RF smart dimmer 306, the RF smart dimmer implements amethod of association 9300 in which it is first determined if the RFsmart dimmer is associated with a plurality of slave nodes 104, e.g.,slave nodes 104 a and 104 b, and thereby is associated with a pluralityof communication pathways, e.g., communication pathways 702 a and 702 b,in step 6402. If the RF smart dimmer 306 is associated with a pluralityof slave nodes 104 and thereby is associated with a plurality ofcommunication pathways 702, then a communication from the source node706 that is principally directed to, and directly affects, only one ofthe destination nodes 708 a, is transmitted by multicasting thecommunication to all of the nodes associated with the RF smart dimmer instep 9304. I.e., the communication is transmitted by the RF smart dimmer306 through all of the communication pathways, 702 a and 702 b, that theRF smart dimmer is associated with thereby transmitting thecommunication to the slave nodes, 104 a and 104 b, and the destinationnodes, 708 a and 708 b. The communication is then single-casted to onlythe nodes directly affected by the communication in step 9306. I.e., thecommunication is only transmitted by the RF smart dimmer 306 through thecommunication pathway 702 a thereby transmitting the communication tothe slave node 104 a and the destination node 708 a. In this manner, thecommunication of the information to the affected nodes in the system 100is assured by performing a multi-cast prior to a single-cast.

Referring to FIG. 94, in an exemplary embodiment, during operation ofthe RF smart dimmer 306, the RF smart dimmer implements a method ofchild protection 9400 in which it is first determined if the RF smartdimmer has active child protection functionality in step 9402. If the RFsmart dimmer 306 has active child protection functionality, then it isthen determined if the RF smart dimmer has sequence control or remotecontrol child protection functionality in step 9404.

If the RF smart dimmer 306 has sequence control child protectionfunctionality, then, in order to permit local manual operation of theswitch, a user must depress the touchpad 8210 three times in step 9406.If a user of the RF smart dimmer 306 depresses the touchpad 8210 threetimes in step 9406, then local manual operation of the RF smart dimmeris permitted in step 9408.

Alternatively, if the RF smart dimmer 306 has remote control childprotection functionality, then, local manual operation of the RF smartdimmer is not permitted. Consequently, if the RF smart dimmer 306 hasremote control child protection functionality, then local manualoperation of the RF smart dimmer is not permitted in step 9410. As aresult, control of the RF smart dimmer 306 is provided by one or more ofthe master nodes 102 of the system 100.

Referring to FIGS. 95 a to 95 b, in an exemplary embodiment, duringoperation of the RF smart dimmer 306, the RF smart dimmer implements amethod of panic mode operation method 9500 in which it is firstdetermined if a panic mode operation has been selected by a user of thesystem 100 in step 9502. In an exemplary embodiment, a panic modeoperation may be selected by a user of the system 100 by operating oneor more of the master nodes 102 of the system.

If a panic mode operation has been selected by a user of the system 100,then the RF smart dimmer 306 is operated in accordance with theoperating parameters assigned to the RF smart dimmer during a panic modeof operation as, for example, contained within the panic database 7310,in step 9504. If the touchpad 8210 of the RF smart dimmer 306 is thendepressed in step 9506, then the RF smart dimmer is operated to decouplethe load 8232 from the power supply 8230 in step 9508. The panic mode ofoperation is then canceled in step 9510.

Alternatively, if the touchpad 8210 of the RF smart dimmer 306 is notthen depressed in step 9506, then, if the panic mode of operation iscanceled by a master node 102 of the system in step 9512, then the RFsmart dimmer is operated to decouple the load 8232 from the power supply8230 in step 9514. The panic mode of operation is then canceled in step9516.

Alternatively, if the panic mode of operation is not canceled by amaster node 102 of the system in step 9512, then the RF smart dimmer 306is operated in accordance with the panic mode duty cycle settings forthe RF smart dimmer contained within, for example, the panic database7310, in step 9518. In an exemplary embodiment, the panic mode dutycycle settings define an amount of time to couple the load 8232 to thepower supply 8230 and an amount of time to decouple the load from thepower supply. For example, if the load 8232 is a light, operation of theRF smart dimmer 306 in a panic mode of operation will turn the light onand off in accordance with the panic mode duty cycle settings for the RFsmart dimmer. If a panic mode of operation is canceled by a user of thesystem 100 in step 9520, then the operation of the RF smart dimmer 306will return to normal in step 9522.

Referring to FIG. 96, in an exemplary embodiment, during operation ofthe RF smart dimmer 306, the RF smart dimmer implements a method of lossof power detection method 9600 in which it is first determined if a lossof power has occurred, for example, by monitoring the power supply 8230in step 9602. If a loss of power is detected in step 9602, then thecurrent operational state of the RF smart dimmer 306 is stored in the RFsmart dimmer operational state database 7312 within the non-volatilememory 8206 of the RF smart dimmer in step 9604. It is then determinedif power has been restored to the RF smart dimmer 306, for example, bymonitoring the power supply 8230 in step 9606. If power has beenrestored to the RF smart dimmer 306, then the current operational stateof the RF smart dimmer is retrieved from the RF switch operational statedatabase 7312 within the non-volatile memory 8206, and the operationalstate of the RF smart dimmer is restored to the operational statedefined within the RF smart dimmer operational state database 7312 instep 9608.

In an exemplary embodiment, the design, operation and functionality ofthe on/off switch 8210, the install button 8212, the uninstall button8214, and the associate button 8218 may be combined into a single pushbutton.

Referring now to FIG. 97, an exemplary embodiment of a battery poweredRF switch 308 includes a controller 9702 that is operably coupled to: amemory 9704, including a non-volatile memory 9706, an RF transceiver9708, a light switch touch pad 9710, an install button 9712, anuninstall button 9714, an LED indicator light 9716, an associate button9718, a network interface 9720, and a battery 9722. In an exemplaryembodiment, the battery powered RF switch 308 is operably coupled to andcontrols the operation of a device that is associated with the batterypowered RF switch such as, for example, an RF receptacle 9724 thatcontrollably operably couples a load 9726 to a power supply 9728.

In an exemplary embodiment, the controller 9702 is adapted to monitorand control the operation of the memory 9704 including a non-volatilememory 9706, the RF transceiver 9708, the light switch touch pad 9710,the install button 9712, the uninstall button 9714, the LED indicatorlight 9716, the associate button 9718, and the network interface 9720.In an exemplary embodiment, the controller 9702 includes one or more ofthe following: a conventional programmable general purpose controller,an application specific integrated circuit (ASIC), or other conventionalcontroller devices. In an exemplary embodiment, the controller 9702includes a model ZW0201 controller, commercially available from ZensysA/S.

Referring now to FIG. 98, in an exemplary embodiment, the controller9702 includes an operating system 9802, application programs 9804, and aboot loader 9806. In an exemplary embodiment, the operating system 9802includes a serial communications driver 9802 a, a memory driver 9802 b,a display driver 9802 c, and a button input driver 9802 d. In anexemplary embodiment, the serial communications driver 9802 a controlsserial communications using the RF serial transceiver 9708, the memorydriver 9802 b controls the memory 9704, including the non volatilememory 9706, the display driver 9802 c controls the LED indicator light9716, and the button input driver 9802 d debounces button inputsprovided by a user using one or more of: the light switch touchpad 9710,the install button 9712, the uninstall button 9714, and the associatebutton 9718. In an exemplary embodiment, the serial communicationsdriver 9802 a includes a Z-Wave™ serial API driver that implements aZ-Wave™ serial API protocol. The Z-Wave™ serial API driver thatimplements a Z-Wave™ serial API protocol are both commercially availablefrom Zensys A/S.

In an exemplary embodiment, the application programs 9804 include astate engine 9804 a. In an exemplary embodiment, the state engine 9804 apermits a user of one or more of the master nodes 102 to configure,control and monitor the operation of the battery powered RF switch 308.

Referring now to FIG. 99, in an exemplary embodiment, the state engine9804 a includes an installation engine 9902, a change of state engine9904, an association engine 9906, a child protection engine 9908, adelayed off engine 9910, a panic mode engine 9912, and a loss of powerdetection engine 9914.

In an exemplary embodiment, the installation engine 9902 monitors theoperating state of the battery powered RF switch 308 and provides anindication to a user of the system 100 as to whether or not the batterypowered RF switch has been installed in the system. In this manner, theinstallation engine 9902 facilitates the installation of the batterypowered RF switch 308 into the system 100.

In an exemplary embodiment, the change of state engine 9904 monitors theoperating state of the battery powered RF switch 308 and, upon a changein operating state, transmits information to one or more of the masternodes 102 regarding the configuration of the battery powered RF switch.

In an exemplary embodiment, the association engine 9906 is adapted tomonitor and control the operation of the battery powered RF switch 308when the battery powered RF switch is associated with one or morecommunication pathway 702.

In an exemplary embodiment, the child protection engine 9908 is adaptedto monitor and control the operation of the battery powered RF switch308 when the battery powered RF switch is operated in a child protectionmode of operation.

In an exemplary embodiment, the delayed off engine 9910 is adapted tomonitor and control the operation of the battery powered RF switch 308when the battery powered RF switch is operated in a delayed off mode ofoperation.

In an exemplary embodiment, the panic mode engine 9912 is adapted tomonitor and control the operation of the battery powered RF switch 308when the battery powered RF switch is operated in a panic mode ofoperation.

In an exemplary embodiment, the loss of power detection engine 9914 isadapted to monitor the operating state of the battery powered RF switch308 and, upon the loss of power, save the operating state of the batterypowered RF switch into the non volatile memory 9706. Upon the resumptionof power to the battery powered RF switch 308, the loss of powerdetection engine 9914 then retrieves the stored operating state of thebattery powered RF switch 308 from the non volatile memory 9706 andrestores the operating state of the battery powered RF switch.

In an exemplary embodiment, the memory 9704, including the non volatilememory 9706, is operably coupled to and controlled by the controller9702. In an exemplary embodiment, as illustrated in FIG. 100, the memory9704, including the non volatile memory 9706, includes a copy of theoperating system 10002, a copy of the application programs 10004, adevice database 10006, a scenes database 10008, an events database10010, an away database 10012, and a system database 10014. In anexemplary embodiment, the memory 9704 includes a model 24LC256 nonvolatile memory, commercially available from Microchip.

In an exemplary embodiment, the device database 10006 includesinformation that is specific to the battery powered RF switch 308. In anexemplary embodiment, as illustrated in FIG. 101, the device database10006 includes the node information frame 1702 for the battery poweredRF switch 308, an association database 10102 for the battery powered RFswitch, a child protection database 10104 for the battery powered RFswitch, a delayed off database 10106 for the battery powered RF switch,a panic database 10108 for the battery powered RF switch, and anoperating state database 10110 for the battery powered RF switch. In anexemplary embodiment, the association database 10102 for the batterypowered RF switch 308 includes information regarding the communicationpathways 702 associated with the battery powered RF switch. In anexemplary embodiment, the child protection database 10104 for thebattery powered RF switch 308 includes information regarding theoperating characteristics of the battery powered RF switch when childprotection is enabled. In an exemplary embodiment, the delayed offdatabase 10106 for the battery powered RF switch 308 includesinformation regarding the operating characteristics of the batterypowered RF switch when delayed off is enabled. In an exemplaryembodiment, the panic database 10108 for the battery powered RF switch308 includes information regarding the operating characteristics of thebattery powered RF switch when panic is enabled. In an exemplaryembodiment, the operating state database 10110 for the battery poweredRF switch 308 includes information representative of the operating stateof the battery powered RF switch.

In an exemplary embodiment, the scenes database 10008 includesinformation regarding the scenes 802 that include the battery powered RFswitch 308. In an exemplary embodiment, the events database 10010includes information regarding the events 1002 that include the batterypowered RF switch 308. In an exemplary embodiment, the away database10012 includes information regarding the away group 1402 that includesthe battery powered RF switch 308. In an exemplary embodiment, thesystem database 10014 includes system information that includes thebattery powered RF switch 308.

In an exemplary embodiment, the RF transceiver 9708 is operably coupledto and controlled by the controller 9702. In an exemplary embodiment,the RF transceiver 9708 transmits and receives RF communications to andfrom other master and slave nodes, 102 and 104, respectively. In anexemplary embodiment, the RF transceiver 9708 may, for example, includeone or more of the following: a conventional RF transceiver, and/or themodel ZW0201 RF transceiver commercially available from Zensys A/S.

In an exemplary embodiment, the light switch touch pad 9710 is aconventional light switch touch pad and is operably coupled to andcontrolled and monitored and monitored by the controller 9702. In anexemplary embodiment, the light switch touch pad 9710 permits anoperator of the battery powered RF switch 308, in combination with thesystem 100, to select the desired mode of operation of the receptacle9724 and, correspondingly, the load 9726.

In an exemplary embodiment, the install button 9712 is operably coupledto and controlled and monitored by the controller 9702. In an exemplaryembodiment, the install button 9712 permits an operator of the batterypowered RF switch 308, in combination with the system 100, to installthe battery powered RF switch into the system.

In an exemplary embodiment, the uninstall button 9714 is operablycoupled to and controlled and monitored by the controller 9702. In anexemplary embodiment, the uninstall button 9714 permits an operator ofthe battery powered RF switch 308, in combination with the system 100,to uninstall the battery powered RF switch from the system.

In an exemplary embodiment, the LED indicator light 9716 is operablycoupled to and controlled and monitored by the controller 9702.

In an exemplary embodiment, the associate button 9718 is operablycoupled to and controlled and monitored by the controller 9702. In anexemplary embodiment, the associate button 9718 permits an operator ofthe battery powered RF switch 308, in combination with the system 100,to associate the battery powered RF switch with communication pathways702 in the system.

In an exemplary embodiment, the network interface 9720 is operablycoupled to and controlled and monitored by the controller 9702. In anexemplary embodiment, the network interface 9720 permits an operator ofthe battery powered RF switch 308 to network the battery operated RFswitch with one or more elements within or outside of the system.

In an exemplary embodiment, the battery 9722 is operably coupled to, andprovides electrical power to, all of the elements of the battery poweredRF switch 308. In several exemplary embodiments, the battery 9722 iscombined, or substituted, with other types of portable power suppliessuch as, for example, solar power. In several exemplary embodiments, thebattery 9722 is combined, or substituted, with other types of portablepower generation such as, for example, power generated by capturing thekinetic energy input into the on/off switch 9710 to generate electricalpower.

Referring to FIG. 102, in an exemplary embodiment, during operation ofthe battery powered RF switch 308, the battery powered RF switchimplements a method of installation 10200 in which, if the batterypowered RF switch has been operably coupled to the battery 9722, thenthe LED indicator lights 9716 are operated to indicate this operationalstate in steps 10202 and 10204. Then, if the battery powered RF switch308 has been installed in the system 100, then the LED indicator lights9716 are operated to indicate this operational state in steps 10206 and10208. In an exemplary embodiment, the LED indicator lights 9716 flashon an off to indicate the operational state in steps 10202 and 10204,and the LED indicator lights 9716 are turned on to indicate theoperational state in steps 10206 and 10208. In this manner, an operatorof the system 100 is provided with a visual and highly effectiveindication of the operational state of the battery powered RF switch 308that is local to the battery powered RF switch. This permits aninstaller of the battery powered RF switch 308, in a large house orcommercial building, with an effective means of determining theoperational state of the battery powered RF switch that is both local tothe battery powered RF switch and avoids the need to interrogate amaster node 102 to determine the operational state.

Referring to FIG. 103, in an exemplary embodiment, during operation ofthe battery powered RF switch 308, the battery powered RF switchimplements a method of detecting a change of state 10300 in which, ifthe operating state of the battery powered RF switch has changed, thenthe node information frame 1702 for the battery powered RF switch istransmitted to one or more of the master nodes 102 of the system 100using the RF transceiver 9708 in steps 10302 and 10304.

Referring to FIGS. 104 a-104 b, in an exemplary embodiment, duringoperation of the battery powered RF switch 308, the battery powered RFswitch 308 implements a method of association 10400 in which it is firstdetermined if the battery powered RF switch is associated with aplurality of slave nodes 104, e.g., slave nodes 104 a and 104 b, andthereby is associated with a plurality of communication pathways, e.g.,communication pathways 702 a and 702 b, in step 6402. If the batterypowered RF switch 308 is associated with a plurality of slave nodes 104and thereby is associated with a plurality of communication pathways702, then a communication from the source node 706 that is principallydirected to, and directly affects, only one of the destination nodes 708a, is transmitted by multicasting the communication to all of the nodesassociated with the battery powered RF switch in step 10404. I.e., thecommunication is transmitted by the battery powered RF switch 308through all of the communication pathways, 702 a and 702 b, that thebattery powered RF switch is associated with thereby transmitting thecommunication to the slave nodes, 104 a and 104 b, and the destinationnodes, 708 a and 708 b. The communication is then single-casted to onlythe nodes directly affected by the communication in step 10406. I.e.,the communication is only transmitted by the battery powered RF switch308 through the communication pathway 702 a thereby transmitting thecommunication to the slave node 104 a and the destination node 708 a. Inthis manner, the communication of the information to the affected nodesin the system 100 is assured by performing a multi-cast prior to asingle-cast.

Referring to FIG. 105, in an exemplary embodiment, during operation ofthe battery powered RF switch 308, the battery powered RF switchimplements a method of child protection 10500 in which it is firstdetermined if the battery powered RF switch has active child protectionfunctionality in step 10502. If the battery powered RF switch 308 hasactive child protection functionality, then it is then determined if thebattery powered RF switch has sequence control or remote control childprotection functionality in step 10504.

If the battery powered RF switch 308 has sequence control childprotection functionality, then, in order to permit local manualoperation of the battery powered RF switch, a user must depress thetouchpad 9710 three times in step 10506. If a user of the batterypowered RF switch 308 depresses the touchpad 9710 three times in step10506, then local manual operation of the battery powered RF switch,using the touchpad 9710, is permitted in step 10508.

Alternatively, if the battery powered RF switch 308 has remote controlchild protection functionality, then, local manual operation of thebattery powered RF switch, using the touchpad 9710, is not permitted.Consequently, if the battery powered RF switch 308 has remote controlchild protection functionality, then local manual operation of thebattery powered RF switch, using the touchpad 9710, is not permitted instep 10510. As a result, control of the battery powered RF switch 308 isprovided by one or more of the master nodes 102 of the system 100.

Referring to FIGS. 106 a to 106 c, in an exemplary embodiment, duringoperation of the battery powered RF switch 308, the battery powered RFswitch implements a method of delayed off 10600 in which it is firstdetermined if the touchpad 9710 of the battery powered RF switch is inan on position in step 10602. If the touchpad 9710 of the batterypowered RF switch 308 is in an on position, then it is then determinedif the battery powered RF switch has remote control protection in step10604. If the battery powered RF switch 308 has remote controlprotection, then, local manual operation of the battery powered RFswitch, using the touchpad 9710, is not permitted.

If the battery powered RF switch 308 does not have remote controlprotection, then it is then determined if the battery powered RF switchhas sequence control protection in step 10606. If the battery powered RFswitch 308 has sequence control protection, then, if a user of thebattery powered RF switch depresses the touchpad 9710 of the batterypowered RF switch three times in step 10608 or if the battery powered RFswitch does not have sequence control protection, then it is determinedif the touchpad was depressed for at least some predefined minimum timeperiod in step 10610.

If the touchpad 9710 of the battery powered RF switch 308 was depressedfor at least some predefined minimum time, then it is determined if thetouchpad was also subsequently depressed in step 10612. If the touchpad9710 of the battery powered RF switch 308 was also subsequentlydepressed, then the battery powered RF switch controls the RF receptacle9724 to turn off the load 9726 in step 10614. If the touchpad 9710 ofthe battery powered RF switch 308 was not also subsequently depressed,then it is determined if the battery powered RF switch 308 will becontrolled by one or more of the master nodes 102 in step 10616.

If the battery powered RF switch 308 will be controlled by one or moreof the master nodes 102, then the operational state of the batterypowered RF switch is controlled by one or more of the master nodes 102in step 10618. Alternatively, if the battery powered RF switch 308 willnot be controlled by one or more of the master nodes 102, then the LEDindicator light 9716 of the battery powered RF switch are flashed instep 10620. The battery powered RF switch 308 is then operated tocontrol the RF receptacle 9724 to turn off the load 9726 after apredetermined time period in step 10622, and then the LED indicatorlight 9716 of the battery powered RF switch are turned off in step10624.

Referring to FIGS. 107 a to 107 b, in an exemplary embodiment, duringoperation of the battery powered RF switch 308, the battery powered RFswitch implements a method of panic mode operation method 10700 in whichit is first determined if a panic mode operation has been selected by auser of the system 100 in step 10702. In an exemplary embodiment, apanic mode operation may be selected by a user of the system 100 byoperating one or more of the master nodes 102 of the system.

If a panic mode operation has been selected by a user of the system 100,then the battery powered RF switch 308 is operated in accordance withthe operating parameters assigned to the battery powered RF switchduring a panic mode of operation as, for example, contained within thepanic database 10108, in step 10704. If the touchpad 9710 of the batterypowered RF switch 308 is then depressed in step 10706, then the batterypowered RF switch is operated to control the RF receptacle 9724 todecouple the load 9726 from the power supply 9728 in step 10708. Thepanic mode of operation is then canceled in step 10710.

Alternatively, if the touchpad 9710 of the battery powered RF switch 308is not then depressed in step 10706, then, if the panic mode ofoperation is canceled by a master node 102 of the system in step 10712,then the battery powered RF switch is operated to control the RFreceptacle 9724 to decouple the load 9726 from the power supply 9728 instep 10714. The panic mode of operation is then canceled in step 10716.

Alternatively, if the panic mode of operation is not canceled by amaster node 102 of the system in step 10712, then the battery powered RFswitch 308 is operated in accordance with the panic mode duty cyclesettings for the battery powered RF switch contained within, forexample, the panic database 10108, in step 10718. In an exemplaryembodiment, the panic mode duty cycle settings define an amount of timeto operate the RF receptacle 9724 to couple the load 9726 to the powersupply 9728 and an amount of time to operate the RF receptacle todecouple the load from the power supply. For example, if the load 9726is a light, operation of the battery powered RF switch 308 in a panicmode of operation will turn the light on and off in accordance with thepanic mode duty cycle settings for the battery powered RF switch. If apanic mode of operation is canceled by a user of the system 100 in step10720, then the operation of the battery powered RF switch 308 willreturn to normal in step 10722.

Referring to FIG. 108, in an exemplary embodiment, during operation ofthe battery powered RF switch 308, the battery powered RF switchimplements a method of loss of power detection method 10800 in which itis first determined if a loss of power has occurred, for example, bymonitoring the battery 9722 in step 10802. If a loss of power isdetected in step 10802, then the current operational state of thebattery powered RF switch 308 is stored in the battery powered RF switchoperational state database 10110 within the non-volatile memory 9706 ofthe battery powered RF switch in step 10804. It is then determined ifbattery power has been restored to the battery powered RF switch 308,for example, by monitoring the battery 9722 in step 10806. If batterypower has been restored to the battery powered RF switch 308, then thecurrent operational state of the battery powered RF switch 308 isretrieved from the battery powered RF switch operational state database10110 within the non-volatile memory 9706, and the operational state ofthe battery powered RF switch is restored to the operational statedefined within the battery powered RF switch operational state database10110 in step 10808.

In an exemplary embodiment, the design, operation and functionality ofthe on/off switch 9710, the install button 9712, the uninstall button9714, and the associate button 9718 may be combined into a single pushbutton.

In an exemplary embodiment, the battery operated RF switch 308 includesone or more elements and/or operational aspects of the RF smart dimmer306.

Referring now to FIG. 109, an exemplary embodiment of an RF dimmer 310includes a controller 10902 that is operably coupled to: a memory 10904,including a non-volatile memory 10906, an RF transceiver 10908, a lightswitch touch pad 10910, an install button 10912, an uninstall button10914, an LED indicator light 10916, an associate button 10918, anetwork interface 10920, a brighten button 10922, a dimmer button 10924,and a loss of power detector 10926. In an exemplary embodiment, aconventional power supply 10930 is operably coupled to the RF dimmer 310for powering the operation of the RF dimmer, and the RF dimmercontrollably couples and decouples a load 10932 to and from the powersupply.

In an exemplary embodiment, the controller 10902 is adapted to monitorand control the operation of the memory 10904, including a non-volatilememory 10906, the RF transceiver 10908, the light switch touch pad10910, the install button 10912, the uninstall button 10914, the LEDindicator light 10916, the associate button 10918, the network interface10920, the brighten button 10922, the dimmer button 10924, and the lossof power detector 10926. In an exemplary embodiment, the controller10902 includes one or more of the following: a conventional programmablegeneral purpose controller, an application specific integrated circuit(ASIC), or other conventional controller devices. In an exemplaryembodiment, the controller 10902 includes a model ZW0201 controller,commercially available from Zensys A/S.

Referring now to FIG. 110, in an exemplary embodiment, the controller10902 includes an operating system 11002, application programs 11004,and a boot loader 11006. In an exemplary embodiment, the operatingsystem 11002 includes a serial communications driver 11002 a, a memorydriver 11002 b, a display driver 11002 c, and a button input driver11002 d. In an exemplary embodiment, the serial communications driver11002 a controls serial communications using the RF serial transceiver10908, the memory driver 11002 b controls the memory 10904, includingthe non volatile memory 10906, the display driver 11002 c controls theLED indicator light 10916, and the button input driver 11002 d debouncesbutton inputs provided by a user using one or more of: the light switchtouchpad 10910, the install button 10912, the uninstall button 10914,the associate button 10918, the brighten button 10922, and the dimmerbutton 10924. In an exemplary embodiment, the serial communicationsdriver 11002 a includes a Z-Wave™ serial API driver that implements aZ-Wave™ serial API protocol. The Z-Wave™ serial API driver thatimplements a Z-Wave™ serial API protocol are both commercially availablefrom Zensys A/S.

In an exemplary embodiment, the application programs 11004 include astate engine 11004 a. In an exemplary embodiment, the state engine 11004a permits a user of one or more of the master nodes 102 to configure,control and monitor the operation of the RF dimmer 310.

Referring now to FIG. 111, in an exemplary embodiment, the state engine11004 a includes an installation engine 11102, a change of state engine11104, an association engine 11106, a child protection engine 11108, adelayed off engine 11110, a panic mode engine 11112, and a loss of powerdetection engine 11114.

In an exemplary embodiment, the installation engine 11102 monitors theoperating state of the RF dimmer 310 and provides an indication to auser of the system 100 as to whether or not the RF dimmer has beeninstalled in the system. In this manner, the installation engine 11102facilitates the installation of the RF dimmer 310 into the system 100.

In an exemplary embodiment, the change of state engine 11104 monitorsthe operating state of the RF dimmer 310 and, upon a change in operatingstate, transmits information to one or more of the master nodes 102regarding the configuration of the RF dimmer.

In an exemplary embodiment, the association engine 11106 is adapted tomonitor and control the operation of the RF dimmer 310 when the RFdimmer is associated with one or more communication pathway 702.

In an exemplary embodiment, the child protection engine 11108 is adaptedto monitor and control the operation of the RF dimmer 310 when the RFdimmer is operated in a child protection mode of operation.

In an exemplary embodiment, the delayed off engine 11110 is adapted tomonitor and control the operation of the RF dimmer 310 when the RFdimmer is operated in a delayed off mode of operation.

In an exemplary embodiment, the panic mode engine 11112 is adapted tomonitor and control the operation of the RF dimmer 310 when the RFdimmer is operated in a panic mode of operation.

In an exemplary embodiment, the loss of power detection engine 11114 isadapted to monitor the operating state of the RF dimmer 310 and, uponthe loss of power, save the operating state of the RF dimmer into thenon volatile memory 10906. Upon the resumption of power to the RF dimmer310, the loss of power detection engine 11114 then retrieves the storedoperating state of the RF dimmer 310 from the non volatile memory 10906and restores the operating state of the RF dimmer.

In an exemplary embodiment, the memory 10904, including the non volatilememory 10906, is operably coupled to and controlled by the controller10902. In an exemplary embodiment, as illustrated in FIG. 112, thememory 10904, including the non volatile memory 10906, includes a copyof the operating system 11202, a copy of the application programs 11204,a device database 11206, a scenes database 11208, an events database11210, an away database 11212, and a system database 11214. In anexemplary embodiment, the memory 10904 includes a model 24LC256 nonvolatile memory, commercially available from Microchip.

In an exemplary embodiment, the device database 11206 includesinformation that is specific to the RF dimmer 310. In an exemplaryembodiment, as illustrated in FIG. 113, the device database 11206includes the node information frame 1702 for the RF dimmer 310, adelayed off database 11304 for the RF dimmer, an association database11306 for the RF dimmer, a child protection database 11308 for the RFdimmer, a panic database 11310 for the RF dimmer, and an operating statedatabase 11312 for the RF dimmer. In an exemplary embodiment, thedelayed off database 11304 for the RF dimmer 310 includes informationregarding the operating characteristics of the RF dimmer when delayedoff is enabled. In an exemplary embodiment, the association database11306 for the RF dimmer 310 includes information regarding thecommunication pathways 702 associated with the RF dimmer. In anexemplary embodiment, the child protection database 11308 for the RFdimmer 310 includes information regarding the operating characteristicsof the RF dimmer when child protection is enabled. In an exemplaryembodiment, the panic database 11310 for the RF dimmer 310 includesinformation regarding the operating characteristics of the RF dimmerwhen panic is enabled. In an exemplary embodiment, the operating statedatabase 11312 for the RF dimmer 310 includes information representativeof the operating state of the RF dimmer.

In an exemplary embodiment, the scenes database 11208 includesinformation regarding the scenes 802 that include the RF dimmer 310. Inan exemplary embodiment, the events database 11210 includes informationregarding the events 1002 that include the RF dimmer 310. In anexemplary embodiment, the away database 11212 includes informationregarding the away group 1402 that includes the RF dimmer 310. In anexemplary embodiment, the system database 11214 includes systeminformation that includes the RF dimmer 310.

In an exemplary embodiment, the RF transceiver 10908 is operably coupledto and controlled by the controller 10902. In an exemplary embodiment,the RF transceiver 10908 transmits and receives RF communications to andfrom other master and slave nodes, 102 and 104, respectively. In anexemplary embodiment, the RF transceiver 10908 may, for example, includeone or more of the following: a conventional RF transceiver, and/or themodel ZW0201 RF transceiver commercially available from Zensys A/S.

In an exemplary embodiment, the light switch touch pad 10910 is aconventional light switch touch pad and is operably coupled to andcontrolled and monitored by the controller 10902. In an exemplaryembodiment, the light switch touch pad 10910 permits an operator of theRF dimmer 310, in combination with the system 100, to select the desiredmode of operation of the load 10932.

In an exemplary embodiment, the install button 10912 is operably coupledto and controlled and monitored by the controller 10902. In an exemplaryembodiment, the install button 10912 permits an operator of the RFdimmer 310, in combination with the system 100, to install the RF dimmerinto the system.

In an exemplary embodiment, the uninstall button 10914 is operablycoupled to and controlled and monitored by the controller 10902. In anexemplary embodiment, the uninstall button 10914 permits an operator ofthe RF dimmer 310, in combination with the system 100, to uninstall theRF dimmer from the system.

In an exemplary embodiment, the LED indicator light 10916 is operablycoupled to and controlled and monitored by the controller 10902.

In an exemplary embodiment, the associate button 10918 is operablycoupled to and controlled and monitored by the controller 10902. In anexemplary embodiment, the associate button 10918 permits an operator ofthe RF dimmer 310, in combination with the system 100, to associate theRF dimmer with communication pathways 702 in the system.

In an exemplary embodiment, the network interface 10920 is operablycoupled to and controlled and monitored by the controller 10902. In anexemplary embodiment, the network interface 10920 permits the RF dimmer310, in combination with the system 100, to be networked with otherdevice within and outside of the system.

In an exemplary embodiment, the brighten button 10922 is operablycoupled to and controlled and monitored by the controller 10902. In anexemplary embodiment, the brighten button 10922 permits an operator ofthe RF dimmer 310, in combination with the system 100, to increase thelevel of current provided by the power supply 10930 to the load 10932.

In an exemplary embodiment, the dimming button 10924 is operably coupledto and controlled and monitored by the controller 10902. In an exemplaryembodiment, the dimming button 10924 permits an operator of the RFdimmer 310, in combination with the system 100, to decrease the level ofcurrent provided by the power supply 10930 to the load 10932.

In an exemplary embodiment, the loss of power detector 10926 is operablycoupled to and controlled and monitored by the controller 10902. In anexemplary embodiment, the loss of power detector 10926 permits anoperator of the RF dimmer 310, in combination with the system 100, todetect a loss of electrical power from the power supply 10930.

Referring to FIG. 114, in an exemplary embodiment, during operation ofthe RF dimmer 310, the RF dimmer implements a method of installation11400 in which, if the RF dimmer has been operably coupled to the powersupply 10230, then the LED indicator lights 10916 are operated toindicate this operational state in steps 11402 and 11404. Then, if theRF dimmer 310 has been installed in the system 100, then the LEDindicator lights 10916 are operated to indicate this operational statein steps 11406 and 11408. In an exemplary embodiment, the LED indicatorlights 10916 flash on an off to indicate the operational state in steps11402 and 11404, and the LED indicator lights 10916 are turned on toindicate the operational state in steps 11406 and 11408. In this manner,an operator of the system 100 is provided with a visual and highlyeffective indication of the operational state of the RF dimmer 310 thatis local to the RF dimmer. This permits an installer of the RF dimmer310, in a large house or commercial building, with an effective means ofdetermining the operational state of the RF dimmer that is both local tothe RF dimmer and avoids the need to interrogate a master node 102 todetermine the operational state.

Referring to FIG. 115, in an exemplary embodiment, during operation ofthe RF dimmer 310, the RF dimmer implements a method of operation 11500in which it is determined if the on/off switch 10910 of the RF dimmerhas been depressed in step 11502. If the on/off switch 10910 of the RFdimmer 310 has been depressed, then it is determined if the RF dimmerhas been installed in the system 100 in step 11504. If the RF dimmer 310has been installed in the system 100, then the node information frame1702 for the RF dimmer is transmitted to one or more of the master nodes102 of the system 100 using the RF transceiver 10908 in step 11506.

Alternatively, if the RF dimmer 310 has not been installed in the system100, or after the node information frame 1702 for the RF dimmer istransmitted to one or more of the master nodes 102 of the system 100, itis determined if the on/off switch 10910 of the RF dimmer has beenreleased in step 11508. If the on/off switch 10910 of the RF dimmer 310has been released, then the RF dimmer operably gradually couples thepower supply 10930 to the load 10932 in accordance with the presetlevels in step 11510. For example, if the load 10932 is a light, in step11510, the RF dimmer 310 gradually increases the lighting level of thelight to the preset level.

Referring to FIGS. 116, in an exemplary embodiment, during operation ofthe RF dimmer 310, the RF dimmer implements a method of operation 11600in which it is determined if the RF dimmer 310 is operably coupling thepower supply 10930 to the load 10932 in step 11602. For example, if theload 10932 is a light, in step 11602, it is determined if the light ison. If the RF dimmer 310 is operably coupling the power supply 10930 tothe load 10932, then it is determined if a user of the RF dimmer 310 hasdepressed the brighten or dimming buttons, 10922 or 10924, respectively,in step 11604. If a user of the RF dimmer 310 has depressed the brightenor dimming buttons, 10922 or 10924, respectively, then the RF dimmerincreases or decreases the level of current supplied to the load 8232 bythe power supply 8203 in step 11606. For example, in step 11606, if theload 10932 is a light, then, if the brighten button 10922 was depressed,the lighting level is increased. Alternatively, for example, in step11606, if the load 10932 is a light, then, if the dimming button 10924was depressed, the lighting level is decreased.

Referring to FIGS. 117 a to 117 c, in an exemplary embodiment, duringoperation of the RF dimmer 310, the RF dimmer implements a method ofdelayed off 11700 in which it is first determined if the touchpad 10910of the RF dimmer is in an on position in step 11702. If the touchpad10910 of the RF dimmer 310 is in an on position, then it is thendetermined if the RF dimmer has remote control protection in step 11704.If the RF dimmer 310 has remote control protection, then, local manualoperation of the RF dimmer is not permitted.

If the RF dimmer 310 does not have remote control protection, then it isthen determined if the RF dimmer has sequence control protection in step11706. If the RF dimmer 310 has sequence control protection, then, if auser of the RF dimmer depresses the touchpad 10910 of the RF dimmerthree times in step 11708 or if the RF dimmer does not have sequencecontrol protection, then it is determined if the touchpad was depressedfor at least some predefined minimum time period in step 11710.

If the touchpad 11710 of the RF dimmer 310 was depressed for at leastsome predefined minimum time, then it is determined if the touchpad wasalso subsequently depressed in step 11712. If the touchpad 10910 of theRF dimmer 310 was also subsequently depressed, then the load 10932 thatis operably coupled to the RF dimmer 310 is turned off in step 11714. Ifthe touchpad 10910 of the RF dimmer 310 was not also subsequentlydepressed, then it is determined if the RF dimmer 310 will be controlledby one or more of the master nodes 102 in step 11716.

If the RF dimmer 310 will be controlled by one or more of the masternodes 102, then the operational state of the RF dimmer is controlled byone or more of the master nodes 102 in step 11718. Alternatively, if theRF dimmer 310 will not be controlled by one or more of the master nodes102, then the LED indicator light 10916 of the RF dimmer are flashed instep 11720. The RF dimmer 310 is then operated to turn off the load10932 operably coupled to the RF dimmer after a predetermined timeperiod in step 11722, and then the LED indicator light 10916 of the RFdimmer are turned off in step 11724.

Referring to FIGS. 118 a-118 b, in an exemplary embodiment, duringoperation of the RF dimmer 310, the RF dimmer implements a method ofassociation 11800 in which it is first determined if the RF dimmer isassociated with a plurality of slave nodes 104, e.g., slave nodes 104 aand 104 b, and thereby is associated with a plurality of communicationpathways, e.g., communication pathways 702 a and 702 b, in step 11802.If the RF dimmer 310 is associated with a plurality of slave nodes 104and thereby is associated with a plurality of communication pathways702, then a communication from the source node 706 that is principallydirected to, and directly affects, only one of the destination nodes 708a, is transmitted by multicasting the communication to all of the nodesassociated with the RF smart dimmer in step 9304. I.e., thecommunication is transmitted by the RF dimmer 310 through all of thecommunication pathways, 702 a and 702 b, that the RF dimmer isassociated with thereby transmitting the communication to the slavenodes, 104 a and 104 b, and the destination nodes, 708 a and 708 b. Thecommunication is then single-casted to only the nodes directly affectedby the communication in step 11806. I.e., the communication is onlytransmitted by the RF dimmer 310 through the communication pathway 702 athereby transmitting the communication to the slave node 104 a and thedestination node 708 a. In this manner, the communication of theinformation to the affected nodes in the system 100 is assured byperforming a multi-cast prior to a single-cast.

Referring to FIG. 119, in an exemplary embodiment, during operation ofthe RF dimmer 310, the RF dimmer implements a method of child protection11900 in which it is first determined if the RF dimmer has active childprotection functionality in step 11902. If the RF dimmer 310 has activechild protection functionality, then it is then determined if the RFdimmer has sequence control or remote control child protectionfunctionality in step 11904.

If the RF dimmer 310 has sequence control child protectionfunctionality, then, in order to permit local manual operation of the RFdimmer, a user must depress the touchpad 10910 three times in step11906. If a user of the RF dimmer 310 depresses the touchpad 10910 threetimes in step 11906, then local manual operation of the RF dimmer ispermitted in step 11908.

Alternatively, if the RF dimmer 310 has remote control child protectionfunctionality, then, local manual operation of the RF dimmer is notpermitted. Consequently, if the RF dimmer 310 has remote control childprotection functionality, then local manual operation of the RF dimmeris not permitted in step 11910. As a result, control of the RF dimmer310 is provided by one or more of the master nodes 102 of the system100.

Referring to FIGS. 120 a to 120 b, in an exemplary embodiment, duringoperation of the RF dimmer 310, the RF dimmer implements a method ofpanic mode operation method 12000 in which it is first determined if apanic mode operation has been selected by a user of the system 100 instep 12002. In an exemplary embodiment, a panic mode operation may beselected by a user of the system 100 by operating one or more of themaster nodes 102 of the system.

If a panic mode operation has been selected by a user of the system 100,then the RF dimmer 310 is operated in accordance with the operatingparameters assigned to the RF dimmer during a panic mode of operationas, for example, contained within the panic database 11310, in step12004. If the touchpad 10910 of the RF dimmer 310 is then depressed instep 12006, then the RF dimmer is operated to decouple the load 10932from the power supply 10930 in step 12008. The panic mode of operationis then canceled in step 12010.

Alternatively, if the touchpad 10910 of the RF dimmer 310 is not thendepressed in step 12006, then, if the panic mode of operation iscanceled by a master node 102 of the system in step 12012, then the RFdimmer is operated to decouple the load 10932 from the power supply10930 in step 12014. The panic mode of operation is then canceled instep 12016.

Alternatively, if the panic mode of operation is not canceled by amaster node 102 of the system in step 12012, then the RF dimmer 310 isoperated in accordance with the panic mode duty cycle settings for theRF dimmer contained within, for example, the panic database 11310, instep 12018. In an exemplary embodiment, the panic mode duty cyclesettings define an amount of time to couple the load 10932 to the powersupply 10930 and an amount of time to decouple the load from the powersupply. For example, if the load 10932 is a light, operation of the RFdimmer 310 in a panic mode of operation will turn the light on and offin accordance with the panic mode duty cycle settings for the RF dimmer.If a panic mode of operation is canceled by a user of the system 100 instep 12020, then the operation of the RF dimmer 310 will return tonormal in step 12022.

Referring to FIG. 121, in an exemplary embodiment, during operation ofthe RF dimmer 310, the RF dimmer implements a method of loss of powerdetection method 12100 in which it is first determined if a loss ofpower has occurred, for example, by monitoring the power supply 10930 instep 12102. If a loss of power is detected in step 12102, then thecurrent operational state of the RF dimmer 310 is stored in the RFdimmer operational state database 11312 within the non-volatile memory10906 of the RF dimmer in step 12104. It is then determined if power hasbeen restored to the RF dimmer 310, for example, by monitoring the powersupply 10930 in step 12106. If power has been restored to the RF dimmer310, then the current operational state of the RF dimmer is retrievedfrom the RF dimmer operational state database 11312 within thenon-volatile memory 10906, and the operational state of the RF dimmer isrestored to the operational state defined within the RF dimmeroperational state database 11312 in step 12108.

Referring to FIG. 122, an exemplary embodiment of an RF thermostat 312includes a conventional commercially available RF thermostat that isoperably coupled to a conventional HVAC system 12202 and a conventionalpower supply 12204. In an exemplary embodiment, the RF thermostat 312 isadapted to monitor and control the operation of the HVAC system 12202 ina conventional manner while operating in the system 100 under thecontrol of one or more of the master nodes 102.

In an exemplary embodiment, the RF thermostat 312 is further adapted toimplement one or more of the operational aspects of one or more of theRF switch 302, the RF receptacle 304, the RF smart dimmer 306, thebattery operated RF switch 308, and the RF dimmer 310.

In an exemplary embodiment, one or more of the slave nodes 104 of thesystem 100 are adapted to control and/or monitor the operation of one ormore other slave nodes. In this manner, one or more of the slave nodes104 of the system 100 may act as surrogate master nodes for one or moreof the other slave nodes of the system.

Referring to FIG. 123, an exemplary embodiment of a control system 12300includes the control system 100 and one or more slave nodes 12302operably coupled to one or more of the master nodes 102 of the controlsystem 100.

Referring to FIG. 124, in an exemplary embodiment, one or more of themaster nodes 102 include a power line communication interface (PLC)12402 that is operably coupled to PLC interfaces 12302 a, provided ineach of the slave nodes, e.g., 12302 _(i), 12302 _(i+1), and 12302 _(N),for communication with the slave nodes, using a conventional powersupply circuit 12404, including a neutral terminal 12406, a hot terminal12408, and a load 12410 coupled to the neutral and hot terminals.

Referring to FIG. 125, in an exemplary embodiment, during operation ofthe control system 12300, the master node 102 communicates with one ormore of the slave nodes 12302 using the loop current 12502 of the powersupply circuit 12404 and the slave nodes communicate with the masternode 102 using the loop voltage 12504 of the power supply circuit. Inparticular, master to slave communication 12506 occurs when the linevoltage 12508 of the power supply circuit 12404 has zero crossings 12510and slave to master communication 12512 occurs when the line voltage12508 of the power supply circuit 12404 has zero crossings 12514.

In an exemplary embodiment, those elements and operational aspects ofthe control system 12300 that relate to and support the master to slavecommunication 12506 and the slave to master communication 12512 areprovided as disclosed in U.S. Pat. No. 6,815,625, the disclosure ofwhich is incorporated herein by reference.

In an exemplary embodiment, the slave nodes 12302 of the control system12300 include one or more of the following: the RF switch 302, the RFreceptacle 304, the RF smart dimmer 306, the battery operated RF switch308, the RF dimmer 310, and/or the RF thermostat 312 with the networkinterfaces, 5720, 6920, 8220, 9720, 10920, and/or 12220 including PLCinterfaces 12302 a.

In an exemplary embodiment, one or more of the operational elementsand/or functionalities of the systems 100 and/or 12300 are localizedand/or non-localized to thereby provide a system having elements and/orfunctionalities that are distributed among the elements, e.g., themaster and slave nodes, 102 and 104, respectively, of the system.

In several exemplary embodiment, the radio frequency communicationinterfaces of the systems, 100 and 12300, may in addition, or in thealternative, use other types of signals such as, for example, infrared,acoustic, or other signals that do not employ a power line conductor.

Referring to FIGS. 126 and 127, in an exemplary embodiment, the batterypowered RF switch 308 includes a top housing 12702 that defines upperand lower mounting holes, 12702 a and 12702 b, a bottom housing 12704that defines upper and lower mounting grooves, 12704 a and 12704 b, aprinted circuit board assembly 12706 that includes switch sensor buttons12706 a, a dimmer button 12706 b, and an LED indicator 12706 c, anon/off switch 12708, batteries, 12710 a and 12710 b, a battery retainingbracket 12712, a double-sided adhesive layer 12714, and mounting screws,12716 a and 12716 b.

Referring to FIGS. 128 and 129, in an exemplary embodiment, the batterypowered RF switch 308 is mounted onto a surface 12800 by adhesivelyaffixing the switch to the surface using the adhesive layer 12714,threadably affixing the switch to the surface using the mounting screws,12716 a and 12716 b, and then placing a conventional switch cover faceplate 12802, over and around the periphery of the switch. In thismanner, the battery powered RF switch 308 may be positioned virtuallyanywhere on the surface 12800, and then easily relocate to anotherlocation on the surface or another surface entirely.

Referring to FIGS. 130 and 131, in an exemplary embodiment, the batterypowered RF switch 308 may be mounted onto the surface 12800 next to aconventional wall switch 13002 and then a conventional switch cover faceplate 13004 may be placed, over and around the periphery of theswitches. In this manner, the battery powered RF switch 308 may beganged with conventional wall switches.

Referring to FIGS. 132 and 133, in an exemplary embodiment, the batterypowered RF switch 308 may be mounted onto the surface 12800 next to aplurality of conventional wall switches, 13002 a and 13002 b, and then aconventional switch cover face plate 13202 may be placed, over andaround the periphery of the switches. In this manner, the batterypowered RF switch 308 may be ganged with a plurality of conventionalwall switches.

Referring now to FIGS. 134 a-134 b, in an exemplary embodiment, duringthe operation of the hand held RF controller 202, after a usersequentially selects DEVICES 2004 and ASSOCIATE 2004 b, using themenu-based program 2000, the controller implements a method 13400 inwhich the controller permits a user to associate devices, such as, forexample, master and slave nodes, 102 and 104, respectively, to define acommunication pathway 702 within the system 100. In particular, in step13402 a user of the hand held RF controller 202 may select a source node706 for the communication pathway 702. After a user of the hand held RFcontroller 202 selects a source node 706 for the communication pathway702, if the source node is a battery power device such as, for example,the battery powered RF switch 308, the user of the hand held RFcontroller 202 will then depress the associate button on the batterypowered source node 706 in step 13406.

If the source node 706 is not a battery power device or after the userof the hand held RF controller 202 has depressed the associate button onthe battery powered source node, then the user of the hand held RFcontroller may select a destination node 708 for the communicationpathway 702 in step 13408. After a user of the hand held RF controller202 has selected a destination node 708 for the communication pathway702, then the configuration of the communication pathways is loaded intorespective memories of the controller, the source node 706, and thedestination node in step 13410.

It is understood that variations may be made in the foregoing withoutdeparting from the scope of the disclosure.

Any foregoing spatial references such as, for example, “upper,” “lower,”“above,” “below,” “rear,” “between,” “vertical,” “angular,” etc., arefor the purpose of illustration only and do not limit the specificorientation or location of the structure described above.

In several exemplary embodiments, it is understood that one or more ofthe operational steps in each embodiment may be omitted. Moreover, insome instances, some features of the present disclosure may be employedwithout a corresponding use of the other features. Moreover, it isunderstood that one or more of the above-described embodiments and/orvariations may be combined in whole or in part with any one or more ofthe other above-described embodiments and/or variations.

Although exemplary embodiments of this disclosure have been described indetail above, those skilled in the art will readily appreciate that manyother modifications, changes and/or substitutions are possible in theexemplary embodiments without materially departing from the novelteachings and advantages of this disclosure. Accordingly, all suchmodifications, changes and/or substitutions are intended to be includedwithin the scope of this disclosure as defined in the following claims.In the claims, means-plus-function clauses are intended to cover thestructures described herein as performing the recited function and notonly structural equivalents, but also equivalent structures.

1. A system for controlling the operation of one or more slave nodesusing one or more remote master nodes, comprising: a communicationinterface for operably coupling the slave nodes and the remote masternodes comprising: a radio frequency communication interface; and a powerline communication interface.
 2. A control system, comprising: one ormore master nodes; a plurality of slave nodes; at least one radiofrequency communication interface for operably coupling the master andslave nodes; and at least one powerline communication interface foroperably coupling the master and slave nodes; wherein the master node isadapted to remotely control the operation of the slave nodes; whereinone or more of the master nodes comprise: a radio frequencycommunication interface; a memory comprising: an operating system;application programs comprising: a devices program comprising:  aninstall devices program adapted to install one or more of the slavedevices into the system;  an associate devices program adapted toassociate one or more of the slave devices with a communication pathway; an uninstall devices program adapted uninstall one or more of the slavedevices from the system;  a remove devices program adapted to remove oneor more of the slave devices from the system;  a replace devices programadapted to replace one or more of the slave devices of the system withone or more other slave devices;  a control devices program adapted tocontrol the operation of one or more aspects of the slave devices of thesystem;  a child protection devices program adapted to control theoperation of one or more of the slave devices during a child protectionmode of operation; and  an all switch devices program adapted to controlthe operation of one or more of the slave devices during an all switchmode of operation; a scenes program comprising:  a create scenes programadapted to create one or more scenes;  a delete scenes program adaptedto delete one or more scenes;  an edit scenes program adapted to editone or more scenes;  an activate scenes program adapted to activate oneor more scenes; and  a deactivate scenes program adapted to deactivateone or more scenes; an events program comprising:  a create eventsprogram adapted to create one or more events;  a delete events programadapted to delete one or more events;  an edit events program adapted toedit one or more events;  an activate events program adapted to activateone or more events; and  a deactivate events program adapted todeactivate one or more events; a system program comprising:  a systempanic program adapted to control one or more of the slave devices in apanic mode of operation; and  a system replicate program adapted toreplicate one or more of the master devices; an away program comprising: an away edit program adapted to edit the away mode of operation for oneor more of the slave devices;  an away activate program adapted toactivate the away mode of operation for one or more of the slavedevices; and  an away deactivate program adapted to deactivate the awaymode of operation for one or more of the slave devices; and an alldevices on/off program for turning all slave device on/off; and a deviceselection program for selecting a slave device comprising:  a devicecontrol program for turning a slave device on or off;  a device controlprogram for brightening or dimming a slave device; and  a device controlprogram for turning a slave device on or off with a delay; and one ormore databases comprising: a devices database one or more nodeinformation frames corresponding to one or more of the slave devicescomprising:  a generic device class;  a specific device class;  acommand class;  a protection command class;  a version command class;  amanufacturing command class; and  an all switch command class; a scenesdatabase comprising information corresponding to one or more scenes; anevents database comprising information corresponding to one or moreevents; a system database comprising information corresponding to one ormore system wide information; an away database comprising informationcorresponding to an away mode of operation for one or more of the slavedevices; a communications pathway database comprising informationcorresponding to one or more communications pathways associated with oneor more of the slave devices; and a failed node ID listing databasecomprising information corresponding to one or more failed slavedevices; a user interface; and a controller operably coupled to theradio frequency communication interface, the memory and the userinterface comprising: an operating system comprising: a serialcommunications driver adapted to monitor and control the operation ofthe radio frequency communication interface; a memory driver adapted tomonitor and control the operation of the memory; a display driveradapted to monitor and control the operation of the user interface; anda button input driver adapted to monitor and control the operation ofthe user interface; and application programs comprising a menu stateengine comprising: a devices engine adapted to configure and control theoperation of one or more of the slave devices comprising:  an installengine adapted to install one or more of the slave devices into thesystem;  an associate engine adapted to associate one or more of theslave devices with a communication pathway;  an uninstall engine adaptedto uninstall one or more of the slave devices from the system;  a removeengine adapted to remove one or more of the slave devices from thesystem;  a replace engine adapted to replace one or more of the slavedevices of the system with one or more other slave devices;  a controlengine adapted to control the operation of one or more aspects of theslave devices of the system;  a child protection engine adapted tocontrol the operation of one or more of the slave devices during a childprotection mode of operation; and  an all switch engine all switchengine is adapted to control the operation of one or more of the slavedevices during an all switch mode of operation; a scenes engine adaptedto configure and control one or more scenes comprising one or more ofthe slave devices comprising:  a scenes create engine adapted to createone or more scenes;  a scenes delete engine adapted to delete one ormore scenes;  a scenes edit engine adapted to edit one or more scenes; a scenes activate engine adapted to activate one or more scenes; and  ascenes deactivate engine adapted to deactivate one or more scenes; anevents engine adapted to configure and control one or more eventscomprising one or more scenes comprising:  an events create engineadapted to create one or more scenes;  an events delete engine adaptedto delete one or more events;  an events edit engine adapted to edit oneor more events;  an events activate engine adapted to activate one ormore events; and  an events deactivate engine adapted to deactivate oneor more events; a system engine adapted to configure and control one ormore system wide modes of operation comprising:  a panic engine adaptedto control one or more of the slave devices in a panic mode ofoperation; and  a replicate engine adapted to replicate one or more ofthe master devices; and an away engine adapted to configure and controlone or more aspects of an away group of slave devices comprising:  anaway edit engine adapted to edit the away mode of operation for one ormore of the slave devices;  an away activate engine away activate engineis adapted to activate the away mode of operation for one or more of theslave devices; and  an away deactivate engine adapted to deactivate theaway mode of operation for one or more of the slave devices.
 3. A methodfor controlling the operation of one or more slave devices using one ormore remote master devices, comprising: communicating informationbetween and among the master and slave devices comprising radiofrequency communications and power line communications.
 4. A method ofoperating a control system comprising one or more master devices and oneor slave devices, wherein the master devices are adapted to remotelymonitor and control the operation of the slave devices, comprising:providing a communication interface for communicating informationbetween and among the master and slave devices that comprises a radiofrequency communication interface and a powerline communicationinterface; providing a menu state engine in one or more of the masterdevices for controlling the operation of the control system; andallowing a user of the menu state engine to select one of the following:a devices engine, a scenes engine, an events engine, a system engine, oran away engine; if a user of one of the master devices presses an onbutton associated with the master device, then all of the slave devicesin an all on/off group are turned on; if a user of one of the masterdevices presses an off button associated with the master device, thenall of the slave devices in an all on/off group are turned off; if auser of one of the master devices selects a value, then a slave deviceassociated with the selected value is selected for control by the user;if the slave device selected for control may be turned on or off, thenallowing the user to turn the selected slave device on or off; if theslave device selected for control may be turned on or off, then allowingthe user to turn the selected slave device on or off with a time delay;if the slave device selected for control may be dimmed or brightened,then allowing the user to dim or brighten the selected slave device; ifthe slave device selected for control may be dimmed or brightened, thenallowing the user to dim or brighten the selected slave device with atime delay; if the slave device selected for control may be adjusted toa plurality of operational states, then allowing the user to turn theoperational state for the selected slave device, wherein the operationalstate for the selected slave device corresponds to a value; if a user ofone of the master devices selects the devices engine, then permittingthe user to install one or more master or slave devices into the system;if a user of the device to be installed in the system depresses aninstall button associated with the device, then determining if a nodeinformation associated with the device has been received by one of themaster devices; if the node information associated with the device to beinstalled in the system has not been received by one of the masterdevices and if the user of the device depresses a cancel buttonassociated with the device, then canceling the installation of thedevice; if the node information associated with the device to beinstalled in the system has not been received by one of the masterdevices within a timeout, then canceling the installation of the device;if the node information associated with the device to be installed inthe system has been received by one of the master devices within atimeout, then installing the device in the system; if the nodeinformation associated with the device to be installed in the system hasbeen received by one of the master devices within a timeout, theninstalling the device in the system as a system information server; ifthe node information associated with the device to be installed in thesystem has been received by one of the master devices within a timeout,then installing the device in the system as a member of an away group;if a user of one of the master devices selects the devices engine, thenpermitting the user to associate first and second slave devices with acommunication pathway; if a user of the first slave device depresses anassociate button for the first slave device, then determining if a nodeinformation for the first slave device was received by one of the masterdevices; if the node information for the first slave device was receivedby one of the master devices, then determining if a user of the secondslave device depresses an associate button for the second slave device;if a user of the second slave device depresses the associate button forthe second slave device, then determining if a node information for thesecond slave device was received by one of the master devices; if thenode information for the second slave device was received by one of themaster devices, then creating a transmission pathway comprising thefirst and second slave devices; if a user of one of the master devicesselects the devices engine, then permitting the user to uninstall one ormore master or slave devices from the system. if a user of the device tobe uninstalled from the system depresses an uninstall button associatedwith the device, then determining if a node information associated withthe device has been received by one of the master devices; if the nodeinformation associated with the device to be uninstalled from the systemhas not been received by one of the master devices and if the user ofthe device depresses a cancel button associated with the device, thencanceling the uninstallation of the device; if the node informationassociated with the device to be uninstalled from the system has notbeen received by one of the master devices within a timeout, thencanceling the uninstallation of the device; if the node informationassociated with the device to be installed in the system has beenreceived by one of the master devices within a timeout, thenuninstalling the device from the system; if a user of one of the masterdevices selects the devices engine, then permitting the user to removeone or more master or slave devices from the system; if the device to beremoved from the system is designated as a non functioning device, thenremoving the device from the system; if a user of one of the masterdevices selects the devices engine, then permitting the user to replaceone or more first master or slave devices with one or more second masteror slave devices; if the first device to be replaced within the systemis designated as a non functioning device, then replacing the firstdevice with the second device by installing the second device in thesystem; if a user of one of the master devices selects the devicesengine, then permitting the user to child protect one or more of theslave devices; if a user of one of the master devices selects a slavedevice for child protection, then transmitting node information for theselected slave device to one or more of the master devices; if the nodeinformation for the selected slave device is not received by one or moreof the master devices within a timeout, then canceling selecting childprotection; if the node information for the selected slave device isreceived by one or more of the master devices within a timeout, thenpermitting a user of one of the master devices to select a level ofchild protection for the slave device; if a user of one of the masterdevices selects the devices engine, then permitting the user toconfigure one or more of the slave devices; if a user of one of themaster devices selects a slave device to be configured, thentransmitting node information for the selected slave device to one ormore of the master devices; if the node information for the selectedslave device is not received by one or more of the master devices withina timeout, then canceling configuration of the slave device; if the nodeinformation for the selected slave device is received by one or more ofthe master devices within a timeout, then permitting a user of one ofthe master devices to configure the slave device, wherein configuringthe slave device comprises: defining a time delay for changing anoperational state of the slave device; defining a duty cycle for a panicmode of operation for the slave device; and defining whether or not apanic mode of operation is enabled for the slave device; if a user ofone of the master devices selects the devices engine, then permittingthe user to configure one or more of the slave devices for operation inan all switch mode of operation; if a user of one of the master devicesselects a slave device to be configured for operation in an all switchmode of operation, then transmitting node information for the selectedslave device to one or more of the master devices; if the nodeinformation for the selected slave device is not received by one or moreof the master devices within a timeout, then canceling configuration ofthe slave device for operation in an all switch mode of operation; ifthe node information for the selected slave device is received by one ormore of the master devices within a timeout, then permitting a user ofone of the master devices to configure the slave device for operation inan all switch mode of operation, wherein configuring the slave devicefor operation in an all switch mode of operation comprises: definingwhether or not the slave device is part of an all switch group; if theslave device is part of the all switch group, then defining permissiblemodes of the operation of the slave device within the all switch group,wherein the permissible modes of the operation of the slave devicewithin the all switch group comprise: all on only; all off only; and allon and off only; if a user of one of the master devices selects thescenes engine, then permitting the user to create one or more scenes; ifa user of one of the master devices selects creating one or more scenes,then permitting the user to define the scene using one or more of theslave devices; if the one or more slave devices are not controllable,then generating an error message and permitting a user of one of themaster devices to define the scene using one or more other of the slavedevices; if the one or more slave devices are controllable, thenpermitting a user of one of the master devices to define the operationallevel for each of the slave devices within the scene; if a user of oneof the master devices selects the scenes engine, then permitting theuser to delete one or more scenes; if a user of one of the masterdevices selects the scenes engine, then permitting the user to edit oneor more scenes; if a user of one of the master devices selects editingone or more scenes, then permitting the user to define the scene usingone or more of the slave devices; if the one or more slave devices arenot controllable, then generating an error message and permitting a userof one of the master devices to define the scene using one or more otherof the slave devices; if the one or more slave devices are controllable,then permitting a user of one of the master devices to define theoperational level for each of the slave devices within the scene; if auser of one of the master devices selects the scenes engine, thenpermitting the user to activate one or more scenes; if a user of one ofthe master devices selects the scenes engine, then permitting the userto deactivate one or more scenes; if a user of one of the master devicesselects the events engine, then permitting the user to create one ormore events; if a user of one of the master devices selects creating oneor more events, then permitting the user to define the event using oneor more of the scenes; if a user of one of the master devices selectsthe events engine, then permitting the user to delete one or moreevents; if a user of one of the master devices selects the eventsengine, then permitting the user to edit one or more events; if a userof one of the master devices selects the events engine, then permittingthe user to activate one or more events; if a user of one of the masterdevices selects the events engine, then permitting the user todeactivate one or more events; if a user of one of the master devicesselects the system engine, then permitting the user to define a panicgroup for operation in a panic mode of operation; permitting a user ofone of the master devices to select a slave device for inclusion in thepanic group; if a user of one of the master devices selects a slavedevice for inclusion in the panic group, then determining if theselected slave device enables a panic mode of operation; if the selectedslave device enables a panic mode of operation, then adding the selecteddevice to the panic group; if a user of one of the master devicesselects the system engine, then permitting the user to replicate aconfiguration of a first master or slave device into a second master orslave device; if a user of one of the master devices selects the firstand second devices, then transmitting the node information for the firstand second devices to the one master device; if the node information forthe selected first and second devices is not received by one or more ofthe master devices within a timeout, then canceling the replication; ifthe node information for the selected first and second devices isreceived by one or more of the master devices within a timeout,permitting a user of one of the master devices to select the portions ofthe configuration of the first device to be replicated into the seconddevice; if the user of one of the master devices has selected theportions of the configuration of the first device to be replicated intothe second device, then replicating the selected portion of theconfiguration of the first device into the second device; if a user ofone of the master devices selects the away engine, then permitting theuser to edit an away group comprising one or more slave devices foroperating in an away mode of operation; if a user of one of the masterdevices selects the away engine, then permitting the user to activate anaway group comprising one or more slave devices for operating in an awaymode of operation, wherein in the away mode of operation, the slavedevices of the away group are randomly operated by the system to all ofthe possible operational states for each slave device; and if a user ofone of the master devices selects the away engine, then permitting theuser to deactivate an away group comprising one or more slave devicesfor no longer operating in an away mode of operation.
 5. A system forcontrolling the operation of one or more slave devices using one or moreremote master devices, comprising: means for communicating informationbetween and among the master and slave nodes comprising means for radiofrequency communications and means for power line communications.
 6. Asystem for operating a control system comprising one or more masterdevices and one or slave devices, wherein the master devices are adaptedto remotely monitor and control the operation of the slave devices,comprising: means for providing a communication interface forcommunication information between and among the master and slave devicesthat comprises radio frequency communication means and powerlinecommunication means; means for providing a menu state engine in one ormore of the master devices for controlling the operation of the controlsystem; and means for allowing a user of the menu state engine to selectone of the following: a devices engine, a scenes engine, an eventsengine, a system engine, or an away engine; if a user of one of themaster devices presses an on button associated with the master device,then means for all of the slave devices in an all on/off group areturned on; if a user of one of the master devices presses an off buttonassociated with the master device, then means for all of the slavedevices in an all on/off group are turned off; if a user of one of themaster devices selects a value, then means for a slave device associatedwith the selected value is selected for control by the user; if theslave device selected for control may be turned on or off, then meansfor allowing the user to turn the selected slave device on or off; ifthe slave device selected for control may be turned on or off, thenmeans for allowing the user to turn the selected slave device on or offwith a time delay; if the slave device selected for control may bedimmed or brightened, then means for allowing the user to dim orbrighten the selected slave device; if the slave device selected forcontrol may be dimmed or brightened, then means for allowing the user todim or brighten the selected slave device with a time delay; if theslave device selected for control may be adjusted to a plurality ofoperational states, then means for allowing the user to turn theoperational state for the selected slave device, wherein the operationalstate for the selected slave device corresponds to a value; if a user ofone of the master devices selects the devices engine, then means forpermitting the user to install one or more master or slave devices intothe system; if a user of the device to be installed in the systemdepresses an install button associated with the device, then means fordetermining if a node information associated with the device has beenreceived by one of the master devices; if the node informationassociated with the device to be installed in the system has not beenreceived by one of the master devices and if the user of the devicedepresses a cancel button associated with the device, then means forcanceling the installation of the device; if the node informationassociated with the device to be installed in the system has not beenreceived by one of the master devices within a timeout, then means forcanceling the installation of the device; if the node informationassociated with the device to be installed in the system has beenreceived by one of the master devices within a timeout, then means forinstalling the device in the system; if the node information associatedwith the device to be installed in the system has been received by oneof the master devices within a timeout, then means for installing thedevice in the system as a system information server; if the nodeinformation associated with the device to be installed in the system hasbeen received by one of the master devices within a timeout, then meansfor installing the device in the system as a member of an away group; ifa user of one of the master devices selects the devices engine, thenmeans for permitting the user to associate first and second slavedevices with a communication pathway; if a user of the first slavedevice depresses an associate button for the first slave device, thenmeans for determining if a node information for the first slave devicewas received by one of the master devices; if the node information forthe first slave device was received by one of the master devices, thenmeans for determining if a user of the second slave device depresses anassociate button for the second slave device; if a user of the secondslave device depresses the associate button for the second slave device,then means for determining if a node information for the second slavedevice was received by one of the master devices; if the nodeinformation for the second slave device was received by one of themaster devices, then means for creating a transmission pathwaycomprising the first and second slave devices; if a user of one of themaster devices selects the devices engine, then means for permitting theuser to uninstall one or more master or slave devices from the system.if a user of the device to be uninstalled from the system depresses anuninstall button associated with the device, then means for determiningif a node information associated with the device has been received byone of the master devices; if the node information associated with thedevice to be uninstalled from the system has not been received by one ofthe master devices and if the user of the device depresses a cancelbutton associated with the device, then means for canceling theuninstallation of the device; if the node information associated withthe device to be uninstalled from the system has not been received byone of the master devices within a timeout, then means for canceling theuninstallation of the device; if the node information associated withthe device to be installed in the system has been received by one of themaster devices within a timeout, then means for uninstalling the devicefrom the system; if a user of one of the master devices selects thedevices engine, then means for permitting the user to remove one or moremaster or slave devices from the system; if the device to be removedfrom the system is designated as a non functioning device, then meansfor removing the device from the system; if a user of one of the masterdevices selects the devices engine, then means for permitting the userto replace one or more first master or slave devices with one or moresecond master or slave devices; if the first device to be replacedwithin the system is designated as a non functioning device, then meansfor replacing the first device with the second device by installing thesecond device in the system; if a user of one of the master devicesselects the devices engine, then means for permitting the user to childprotect one or more of the slave devices; if a user of one of the masterdevices selects a slave device for child protection, then means fortransmitting node information for the selected slave device to one ormore of the master devices; if the node information for the selectedslave device is not received by one or more of the master devices withina timeout, then means for canceling selecting child protection; if thenode information for the selected slave device is received by one ormore of the master devices within a timeout, then means for permitting auser of one of the master devices to select a level of child protectionfor the slave device; if a user of one of the master devices selects thedevices engine, then means for permitting the user to configure one ormore of the slave devices; if a user of one of the master devicesselects a slave device to be configured, then means for transmittingnode information for the selected slave device to one or more of themaster devices; if the node information for the selected slave device isnot received by one or more of the master devices within a timeout, thenmeans for canceling configuration of the slave device; if the nodeinformation for the selected slave device is received by one or more ofthe master devices within a timeout, then means for permitting a user ofone of the master devices to configure the slave device, wherein meansfor configuring the slave device comprises: means for defining a timedelay for changing an operational state of the slave device; means fordefining a duty cycle for a panic mode of operation for the slavedevice; and means for defining whether or not a panic mode of operationis enabled for the slave device; if a user of one of the master devicesselects the devices engine, then means for permitting the user toconfigure one or more of the slave devices for operation in an allswitch mode of operation; if a user of one of the master devices selectsa slave device to be configured for operation in an all switch mode ofoperation, then means for transmitting node information for the selectedslave device to one or more of the master devices; if the nodeinformation for the selected slave device is not received by one or moreof the master devices within a timeout, then means for cancelingconfiguration of the slave device for operation in an all switch mode ofoperation; if the node information for the selected slave device isreceived by one or more of the master devices within a timeout, thenmeans for permitting a user of one of the master devices to configurethe slave device for operation in an all switch mode of operation,wherein means for configuring the slave device for operation in an allswitch mode of operation comprises: means for defining whether or notthe slave device is part of an all switch group; if the slave device ispart of the all switch group, then means for defining permissible modesof the operation of the slave device within the all switch group,wherein the permissible modes of the operation of the slave devicewithin the all switch group comprise: all on only; all off only; and allon and off only; if a user of one of the master devices selects thescenes engine, then means for permitting the user to create one or morescenes; if a user of one of the master devices selects creating one ormore scenes, then means for permitting the user to define the sceneusing one or more of the slave devices; if the one or more slave devicesare not controllable, then means for generating an error message andpermitting a user of one of the master devices to define the scene usingone or more other of the slave devices; if the one or more slave devicesare controllable, then means for permitting a user of one of the masterdevices to define the operational level for each of the slave deviceswithin the scene; if a user of one of the master devices selects thescenes engine, then means for permitting the user to delete one or morescenes; if a user of one of the master devices selects the scenesengine, then means for permitting the user to edit one or more scenes;if a user of one of the master devices selects editing one or morescenes, then means for permitting the user to define the scene using oneor more of the slave devices; if the one or more slave devices are notcontrollable, then means for generating an error message and permittinga user of one of the master devices to define the scene using one ormore other of the slave devices; if the one or more slave devices arecontrollable, then means for permitting a user of one of the masterdevices to define the operational level for each of the slave deviceswithin the scene; if a user of one of the master devices selects thescenes engine, then means for permitting the user to activate one ormore scenes; if a user of one of the master devices selects the scenesengine, then means for permitting the user to deactivate one or morescenes; if a user of one of the master devices selects the eventsengine, then means for permitting the user to create one or more events;if a user of one of the master devices selects creating one or moreevents, then means for permitting the user to define the event using oneor more of the scenes; if a user of one of the master devices selectsthe events engine, then permitting the user to delete one or moreevents; if a user of one of the master devices selects the eventsengine, then means for permitting the user to edit one or more events;if a user of one of the master devices selects the events engine, thenmeans for permitting the user to activate one or more events; if a userof one of the master devices selects the events engine, then means forpermitting the user to deactivate one or more events; if a user of oneof the master devices selects the system engine, then means forpermitting the user to define a panic group for operation in a panicmode of operation; means for permitting a user of one of the masterdevices to select a slave device for inclusion in the panic group; if auser of one of the master devices selects a slave device for inclusionin the panic group, then means for determining if the selected slavedevice enables a panic mode of operation; if the selected slave deviceenables a panic mode of operation, then means for adding the selecteddevice to the panic group; if a user of one of the master devicesselects the system engine, then means for permitting the user toreplicate a configuration of a first master or slave device into asecond master or slave device; if a user of one of the master devicesselects the first and second devices, then means for transmitting thenode information for the first and second devices to the one masterdevice; if the node information for the selected first and seconddevices is not received by one or more of the master devices within atimeout, then means for canceling the replication; if the nodeinformation for the selected first and second devices is received by oneor more of the master devices within a timeout, means for permitting auser of one of the master devices to select the portions of theconfiguration of the first device to be replicated into the seconddevice; if the user of one of the master devices has selected theportions of the configuration of the first device to be replicated intothe second device, then means for replicating the selected portion ofthe configuration of the first device into the second device; if a userof one of the master devices selects the away engine, then means forpermitting the user to edit an away group comprising one or more slavedevices for operating in an away mode of operation; if a user of one ofthe master devices selects the away engine, then means for permittingthe user to activate an away group comprising one or more slave devicesfor operating in an away mode of operation, wherein in the away mode ofoperation, the slave devices of the away group are randomly operated bythe system to all of the possible operational states for each slavedevice; and if a user of one of the master devices selects the awayengine, then means for permitting the user to deactivate an away groupcomprising one or more slave devices for no longer operating in an awaymode of operation.
 7. A computer program for controlling the operationof one or more slave devices using one or more remote master devices,comprising program instructions for: communicating information betweenand among the master and slave devices comprising radio frequencycommunications and power line communications.
 8. A computer program foroperating a control system comprising one or more master devices and oneor slave devices, wherein the master devices are adapted to remotelymonitor and control the operation of the slave devices, comprisingprogram instructions for: providing a communication interface betweenand among the master and slave devices that comprises a radio frequencycommunication interface and a powerline communication interface;providing a menu state engine in one or more of the master devices forcontrolling the operation of the control system; and allowing a user ofthe menu state engine to select one of the following: a devices engine,a scenes engine, an events engine, a system engine, or an away engine;if a user of one of the master devices presses an on button associatedwith the master device, then all of the slave devices in an all on/offgroup are turned on; if a user of one of the master devices presses anoff button associated with the master device, then all of the slavedevices in an all on/off group are turned off; if a user of one of themaster devices selects a value, then a slave device associated with theselected value is selected for control by the user; if the slave deviceselected for control may be turned on or off, then allowing the user toturn the selected slave device on or off; if the slave device selectedfor control may be turned on or off, then allowing the user to turn theselected slave device on or off with a time delay; if the slave deviceselected for control may be dimmed or brightened, then allowing the userto dim or brighten the selected slave device; if the slave deviceselected for control may be dimmed or brightened, then allowing the userto dim or brighten the selected slave device with a time delay; if theslave device selected for control may be adjusted to a plurality ofoperational states, then allowing the user to turn the operational statefor the selected slave device, wherein the operational state for theselected slave device corresponds to a value; if a user of one of themaster devices selects the devices engine, then permitting the user toinstall one or more master or slave devices into the system; if a userof the device to be installed in the system depresses an install buttonassociated with the device, then determining if a node informationassociated with the device has been received by one of the masterdevices; if the node information associated with the device to beinstalled in the system has not been received by one of the masterdevices and if the user of the device depresses a cancel buttonassociated with the device, then canceling the installation of thedevice; if the node information associated with the device to beinstalled in the system has not been received by one of the masterdevices within a timeout, then canceling the installation of the device;if the node information associated with the device to be installed inthe system has been received by one of the master devices within atimeout, then installing the device in the system; if the nodeinformation associated with the device to be installed in the system hasbeen received by one of the master devices within a timeout, theninstalling the device in the system as a system information server; ifthe node information associated with the device to be installed in thesystem has been received by one of the master devices within a timeout,then installing the device in the system as a member of an away group;if a user of one of the master devices selects the devices engine, thenpermitting the user to associate first and second slave devices with acommunication pathway; if a user of the first slave device depresses anassociate button for the first slave device, then determining if a nodeinformation for the first slave device was received by one of the masterdevices; if the node information for the first slave device was receivedby one of the master devices, then determining if a user of the secondslave device depresses an associate button for the second slave device;if a user of the second slave device depresses the associate button forthe second slave device, then determining if a node information for thesecond slave device was received by one of the master devices; if thenode information for the second slave device was received by one of themaster devices, then creating a transmission pathway comprising thefirst and second slave devices; if a user of one of the master devicesselects the devices engine, then permitting the user to uninstall one ormore master or slave devices from the system. if a user of the device tobe uninstalled from the system depresses an uninstall button associatedwith the device, then determining if a node information associated withthe device has been received by one of the master devices; if the nodeinformation associated with the device to be uninstalled from the systemhas not been received by one of the master devices and if the user ofthe device depresses a cancel button associated with the device, thencanceling the uninstallation of the device; if the node informationassociated with the device to be uninstalled from the system has notbeen received by one of the master devices within a timeout, thencanceling the uninstallation of the device; if the node informationassociated with the device to be installed in the system has beenreceived by one of the master devices within a timeout, thenuninstalling the device from the system; if a user of one of the masterdevices selects the devices engine, then permitting the user to removeone or more master or slave devices from the system; if the device to beremoved from the system is designated as a non functioning device, thenremoving the device from the system; if a user of one of the masterdevices selects the devices engine, then permitting the user to replaceone or more first master or slave devices with one or more second masteror slave devices; if the first device to be replaced within the systemis designated as a non functioning device, then replacing the firstdevice with the second device by installing the second device in thesystem; if a user of one of the master devices selects the devicesengine, then permitting the user to child protect one or more of theslave devices; if a user of one of the master devices selects a slavedevice for child protection, then transmitting node information for theselected slave device to one or more of the master devices; if the nodeinformation for the selected slave device is not received by one or moreof the master devices within a timeout, then canceling selecting childprotection; if the node information for the selected slave device isreceived by one or more of the master devices within a timeout, thenpermitting a user of one of the master devices to select a level ofchild protection for the slave device; if a user of one of the masterdevices selects the devices engine, then permitting the user toconfigure one or more of the slave devices; if a user of one of themaster devices selects a slave device to be configured, thentransmitting node information for the selected slave device to one ormore of the master devices; if the node information for the selectedslave device is not received by one or more of the master devices withina timeout, then canceling configuration of the slave device; if the nodeinformation for the selected slave device is received by one or more ofthe master devices within a timeout, then permitting a user of one ofthe master devices to configure the slave device, wherein configuringthe slave device comprises: defining a time delay for changing anoperational state of the slave device; defining a duty cycle for a panicmode of operation for the slave device; and defining whether or not apanic mode of operation is enabled for the slave device; if a user ofone of the master devices selects the devices engine, then permittingthe user to configure one or more of the slave devices for operation inan all switch mode of operation; if a user of one of the master devicesselects a slave device to be configured for operation in an all switchmode of operation, then transmitting node information for the selectedslave device to one or more of the master devices; if the nodeinformation for the selected slave device is not received by one or moreof the master devices within a timeout, then canceling configuration ofthe slave device for operation in an all switch mode of operation; ifthe node information for the selected slave device is received by one ormore of the master devices within a timeout, then permitting a user ofone of the master devices to configure the slave device for operation inan all switch mode of operation, wherein configuring the slave devicefor operation in an all switch mode of operation comprises: definingwhether or not the slave device is part of an all switch group; if theslave device is part of the all switch group, then defining permissiblemodes of the operation of the slave device within the all switch group,wherein the permissible modes of the operation of the slave devicewithin the all switch group comprise: all on only; all off only; and allon and off only; if a user of one of the master devices selects thescenes engine, then permitting the user to create one or more scenes; ifa user of one of the master devices selects creating one or more scenes,then permitting the user to define the scene using one or more of theslave devices; if the one or more slave devices are not controllable,then generating an error message and permitting a user of one of themaster devices to define the scene using one or more other of the slavedevices; if the one or more slave devices are controllable, thenpermitting a user of one of the master devices to define the operationallevel for each of the slave devices within the scene; if a user of oneof the master devices selects the scenes engine, then permitting theuser to delete one or more scenes; if a user of one of the masterdevices selects the scenes engine, then permitting the user to edit oneor more scenes; if a user of one of the master devices selects editingone or more scenes, then permitting the user to define the scene usingone or more of the slave devices; if the one or more slave devices arenot controllable, then generating an error message and permitting a userof one of the master devices to define the scene using one or more otherof the slave devices; if the one or more slave devices are controllable,then permitting a user of one of the master devices to define theoperational level for each of the slave devices within the scene; if auser of one of the master devices selects the scenes engine, thenpermitting the user to activate one or more scenes; if a user of one ofthe master devices selects the scenes engine, then permitting the userto deactivate one or more scenes; if a user of one of the master devicesselects the events engine, then permitting the user to create one ormore events; if a user of one of the master devices selects creating oneor more events, then permitting the user to define the event using oneor more of the scenes; if a user of one of the master devices selectsthe events engine, then permitting the user to delete one or moreevents; if a user of one of the master devices selects the eventsengine, then permitting the user to edit one or more events; if a userof one of the master devices selects the events engine, then permittingthe user to activate one or more events; if a user of one of the masterdevices selects the events engine, then permitting the user todeactivate one or more events; if a user of one of the master devicesselects the system engine, then permitting the user to define a panicgroup for operation in a panic mode of operation; permitting a user ofone of the master devices to select a slave device for inclusion in thepanic group; if a user of one of the master devices selects a slavedevice for inclusion in the panic group, then determining if theselected slave device enables a panic mode of operation; if the selectedslave device enables a panic mode of operation, then adding the selecteddevice to the panic group; if a user of one of the master devicesselects the system engine, then permitting the user to replicate aconfiguration of a first master or slave device into a second master orslave device; if a user of one of the master devices selects the firstand second devices, then transmitting the node information for the firstand second devices to the one master device; if the node information forthe selected first and second devices is not received by one or more ofthe master devices within a timeout, then canceling the replication; ifthe node information for the selected first and second devices isreceived by one or more of the master devices within a timeout,permitting a user of one of the master devices to select the portions ofthe configuration of the first device to be replicated into the seconddevice; if the user of one of the master devices has selected theportions of the configuration of the first device to be replicated intothe second device, then replicating the selected portion of theconfiguration of the first device into the second device; if a user ofone of the master devices selects the away engine, then permitting theuser to edit an away group comprising one or more slave devices foroperating in an away mode of operation; if a user of one of the masterdevices selects the away engine, then permitting the user to activate anaway group comprising one or more slave devices for operating in an awaymode of operation, wherein in the away mode of operation, the slavedevices of the away group are randomly operated by the system to all ofthe possible operational states for each slave device; and if a user ofone of the master devices selects the away engine, then permitting theuser to deactivate an away group comprising one or more slave devicesfor no longer operating in an away mode of operation.